2
1
I have a public IP, say, 123.45.67.89 And a private network of 192.168.1.0/24
When I am anywhere outside the private network, I can connect to the public IP. When I am inside the private network, I cannot communicate with the public IP (HTTP/IMAP/etc).
I am told that my DNS should resolve to the private IP from the public IP when inside the network.
Is this true, and how would I go about doing this? On server 2003 (the DNS server) I setup a reverse lookup of 123.45.67.0 and created a pointer of 123.45.67.89 to my private hostname. After an ipconfig /flushdns on a client, this doesn't appear to be working.
I'm quite sure this is way outside what is necessary as I said in a comment above, a simply Linsys router had everything working fine. Once it was replace with an industry grade Cisco router it no longer worked. Although this may work, I do not have a second DNS server. – gpresland – 2011-08-24T16:32:59.763
You are wrong to be quite sure. (If you knew the right answer, you wouldn't be here asking the question, would you?) This is what is necessary.
grawity
is right.MaQleod
has said the same thing. I say the same thing. Heck, you've told us in that self-same comment that your own network administrators have said the same thing to you. Set up the split-horizon DNS service. Your network administrators aren't providing hairpin NAT any more, and have told you to set your DNS servers to provide split-horizon service instead. So do that! – JdeBP – 2011-08-24T21:25:55.923