I've just installed a Linux home server that operates as a private cloud with seafile. The server has a static IP in my LAN (ex. 192.168.1.7) but my ISP provides dynamic IP's, so I bought a DDNS service, added a domain (ex. example.com) and configured the ddns service plus some port forwarding on the router. All works perfectly but I'm unsure about one thing:
If a seafile client within the LAN up-/downloads something to the server via example.com, what route will be used for the data traffic? Is that DNS / Routing stuff smart enough to eventually match example.com to 192.168.1.7 within the local network? If this is not the case and manipulating hosts file on the clients is not an option (mobile devices that should be able to access the cloud from anywhere, or iOS devices), do I have to setup a local DNS Server to gain full LAN speed but retain the ability to be remote?