Issue with DNS using NAT between overlapping networks.
We have two overlapping LANs seperated by two 2600 routers. We're using the 'ip nat inside source static network' command on both routers to perform the address translation.
This has worked fine so far, but we're now having an issue putting a backup domain controller on the remote LAN. When trying to join it to the domain, it makes a DNS request to its DNS server (which is the PDC on the primary LAN) asking for the address of the domain's PDC. The PDC responds with it's own address. The address included in the DNS reply gets translated by the first router (good), but then gets translated again by the second router (bad) which changes the address back to what it was originally. The result of this is that the remote BDC thinks the PDC is on it's own subnet, and hence can't find it.
My understanding is that a Cisco router will translate the response in a DNS reply if it also translates the IP header. In this case, both routers are translating the IP header of the packet (the first router translates the source, the second translates the destination), so the DNS packet gets translated by both routers. So, the question is: is there any way to prevent the DNS reply from being translated on one of the routers while still having that router translate the IP header?
Re: Issue with DNS using NAT between overlapping networks.
An one stop solution to this is to do NAT only in a single router, rather than doing it at two ends.Are the 2600s being used to connect only between the two locations??. Then shift the NATing to just one router. Take a look at this link http://www.cisco.com/warp/public/556/3.html
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...