Reply
Posted Sep 24, 2012
11:27:08 AM
View profile
Unable to access internal network from external address

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?

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?

0
(0)
  • Rate this reply
View profile
Solved
Sep 25, 2012 9:16:22 AM
0
(0)
Guru
http://www.pcreview.co.uk/forums/cant-access-public-website-within-web-server-domain-need-force-nat-t1729841.html
What you want is the have a record in your own DNS Server for these sites' "Domain Names" that resolve to the internal Private IP instead of the Public IP and then make sure that your own DNS is the first DNS Server requested from by these machines. This allows these web servers to communicate directly to each other without involving the Firewall at all (it also allows your internal users to work the same way). The only time that the firewall should be involved is when an outside host makes a request to those machine from the Internet. Any internal machine should *never* have to go to the firewall to get to something that is already positioned physically on the same side of the firewall that the requesting machine is already on.

Possible Fix:
First find out what the IP address is of the external web server if
you do not already know it (You can get it by pinging the
website).

Go to Start > Control Panel > Administrative Tools >
DNS and locate example.com. Right-click and choose “New
Host (A or AAAA)”. Type “www” into the name field, and the IP
address of your external web server into the IP Address field.
Click the “Add Host” button to save it.
Accepted Solution

Unable to access internal network from external address

2,170 views
2 replies
(0) Me too
(0) Me too
Post reply
Cancel
Submit
View all replies
(2)
0
(0)
  • Rate this reply
View profile
Solved
Sep 25, 2012 9:16:22 AM
0
(0)
Guru
http://www.pcreview.co.uk/forums/cant-access-public-website-within-web-server-domain-need-force-nat-...
What you want is the have a record in your own DNS Server for these sites' "Domain Names" that resolve to the internal Private IP instead of the Public IP and then make sure that your own DNS is the first DNS Server requested from by these machines. This allows these web servers to communicate directly to each other without involving the Firewall at all (it also allows your internal users to work the same way). The only time that the firewall should be involved is when an outside host makes a request to those machine from the Internet. Any internal machine should *never* have to go to the firewall to get to something that is already positioned physically on the same side of the firewall that the requesting machine is already on.

Possible Fix:
First find out what the IP address is of the external web server if
you do not already know it (You can get it by pinging the
website).

Go to Start > Control Panel > Administrative Tools >
DNS and locate example.com. Right-click and choose “New
Host (A or AAAA)”. Type “www” into the name field, and the IP
address of your external web server into the IP Address field.
Click the “Add Host” button to save it.
http://www.pcreview.co.uk/forums/cant-access-public-website-within-web-server-domain-need-force-nat-t1729841.html
What you want is the have a record in your own DNS Server for these sites' "Domain Names" that resolve to the internal Private IP instead of the Public IP and then make sure that your own DNS is the first DNS Server requested from by these machines. This allows these web servers to communicate directly to each other without involving the Firewall at all (it also allows your internal users to work the same way). The only time that the firewall should be involved is when an outside host makes a request to those machine from the Internet. Any internal machine should *never* have to go to the firewall to get to something that is already positioned physically on the same side of the firewall that the requesting machine is already on.

Possible Fix:
First find out what the IP address is of the external web server if
you do not already know it (You can get it by pinging the
website).

Go to Start > Control Panel > Administrative Tools >
DNS and locate example.com. Right-click and choose “New
Host (A or AAAA)”. Type “www” into the name field, and the IP
address of your external web server into the IP Address field.
Click the “Add Host” button to save it.

Re: Unable to access internal network from external address

2 of 3 (2,135 Views)
Solution
0
(0)
  • Rate this reply
View profile
Oct 1, 2012 12:55:07 PM
0
(0)
Contributor

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.

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.

Re: Unable to access internal network from external address

3 of 3 (2,085 Views)
Share this post
Share this post