09-24-2012 11:27 AM
I have a server set up that I regularly need to access from outside of my home network. Port forwarding is set up correctly on the router (Motorola NVG510) and it is fully accessible outside of my home network. I use dyndns to keep my IP up-to-date and it is working. However internally (say from my desktop or my laptop connected to my home network) I cannot access it by the full URL (myhost.dyndns.org) and I am forced to use the internal IP. This is inconvenient to have to change every time I need to access the server when going from inside my home to anywhere outside and visa versa. Is there a setting or a way past this so the address will resolve correctly within my own network?
Solved by: Go to Solution.
09-25-2012 9:16 AM
10-01-2012 12:55 PM
Thanks! I hadn't thought of this. I will try it when I get the chance but your right, this seems like it would be the best choice. I think because the server is already registered in DNS however I should use a CNAME record (pointer) instead, but the idea is the same.
10-09-2017 12:09 PM
This is unacceptable for portable devices, however, that automatically switch between an intranet and internet context as you move it around. At least, I've yet to find network settings that let you use a different 'host' file depending on what network it is connected to.
What WOULD be nice is:
1. During DHCP, the AT&T router returned ITSELF as the primary DNS server.
2. The AT&T router then reported the Internal IP Address instead of the external one when requests for those DNS entries are made.
The AT&T router was smart enough to detect that a packet coming from inside the network is bound for somewhere else inside the network, even though the destination address is remote, and routed it properly. The router has all the necessary information to make this determination.
Welcome to the internet boards! Check out our troubleshooting articles below and don’t forget to search the forums - your question may have been answered already!
Service acting up? Click here to troubleshoot now!
For DSL related issues. We highly recommend chatting with our teams to address this as quickly as possible.