[Support]: Inquiry about Supporting Domain Names in custom planet Configuration
📝 Inquiry
Dear ZTNet Team,
I hope this message finds you well. I am currently using the ZTNet project and have encountered a question regarding the configuration of the planet parameter.
In the current implementation, it seems that the planet configuration expects an IP address and port. I was wondering if it is possible to modify this configuration to accept a domain name (with the corresponding port) instead of just the IP address and port.
Just like this:
Could you please let me know:
- Is there any specific reason why
planetonly accepts IP addresses, and is there an option to use a domain name instead? - If it's not directly supported, would it be possible to modify the source code to allow this, and if so, what changes would be necessary?
- Are there any known limitations or issues with using domain names in the
planetconfiguration?
Thank you for your time and assistance. I look forward to your response.
Best regards
🔖 Version
0.7.7
🔧 Deployment Type
- [x] Docker
- [ ] Standalone
💻 Operating System
Other Linux
🌐 Browser
Chrome
📚 Any Other Information That May Be Helpful
No response
ztnet uses the mkworld from kmahyyg. It only supports ip addresses. https://github.com/kmahyyg/ztncui-aio
Dear @dadastory , Sinamics is right. ZtNET is using: ZeroTier. ZeroTier is using a kind of encryption, where the IP address itself is part of the decode-key = important part of security.
But it's not a too big problem, since the cheapest (1CPU + 1GB RAM) VPS is fully enough to run this server including a fix IPv4 address. Also You can back up the system and restore to a new server later.
You can create 2 servers, at 2 different geolocation, renting the VPS from 2 different companies, using 2 different subnets, and if one fails, you can still reach the devices through the 2th one to restore the 1th / 3th.
@sinamics IMHO you can close this ticket.
This issue is stale because it has been open for 30 days with no activity.
This issue was closed because it has been inactive for 3 days since being marked as stale.