I plan to send a device such as a “home server” to customers who are talking to their smartphone (Android or iPhone). The problem is that, depending on the Internet service provider, the client does not have an external IPv4 address (DS-lite tunneling), so the smart phone cannot just use the IPv4 DNS record to search for the server.
Alternatives I can think of:
Make the server use the DynDNS IPv6 service and make IPv6 preferable to IPv4 on the smartphone. Since the solution should work without the client having to register for the DynDNS service, I did not find any services that allow me to do this.
Set up my own "directory server" so that the home server registers its serial number at intervals - the same as DynDNS, but at the application level via HTTPS. Then the client could simply enter the serial number in the application to find the server. Due to authentication / encryption requirements, this solution is more difficult to implement than I like.
Any other ideas on how to make a home server affordable? I would really like to avoid using my "cloud service". Perhaps some type of peer discovery, maybe?
[UPDATE:] This is what I am mainly looking for:
Home server Relay DynDNS Client
| | | |
|-------- open tunnel to port 80 ----->| | |
|<-success, listening on 192.0.2.1:80 -| | |
| | | |
|----- Register "my.ddns.net" ---------------------->| |
|<------------ "my.ddns.net" is now 192.0.2.1 -------| |
| | | |
| |<- GET http://my.ddns.net -|
|<------- GET http://my.ddns.net ----| | |
|--- HTTP response ------------------->| | |
| |----- HTTP response ------>|
source
share