A PC and a webserver are on the same LAN behind a CPE running PAT. All web requests from WAN side are successfully translated and forwarded to the webserver. The PC is able to make port 80 requests to the webserver via private IP, however when the same PC is making port 80 requests to the webserver using DNS (public IP address), the CPE doesn't seem to translate it . Can someone clue me into what configlets I'm missing that can resolve this dilemma? Relevant config as follows
ip address 192.168.0.1 255.255.255.0
ip nat inside
interface ATM0.1 point-to-point
ip address 184.108.40.206 255.255.255.252
ip nat outside
ip nat translation timeout 3600
ip nat inside source list 1 interface ATM0.1 overload
Since you said that the "CPE" wasn't translating, I'll assume the DNS is outside. I think that you probably need to translate the DNS response, which likely includes the public IP of 220.127.116.11 - which doesn't exist on the LAN. I believe NAT can reach into the payload and translate the DNS response to the local address. Check out the very last question in this NAT Q&A and see if it sounds like your issue:
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...