He have three DNS server in our AD environment.
2 in one datacenter
1 in another datacenter
All three are setup with the exact same forwarders in the exact same order.
When we try to do an NSLookup using our three DNS servers as the server to use, for the site uat2.budgettruck.com, we get the following results:
- the two DNS servers in one datacenter return the correct IP of 148.9.81.2 (the correct externally accessible IP)
- the one lone DNS server in our other datacenter returns 10.6.192.16 (the incorrect IP. This is a private IP)
We have cleared the DNS Server Cache, we have tested each forwarder we have configured thinking one of them had an incorrect value, we have verified the owner of the domain budgettruck.com has the correct entries in their DNS zone.
We are at a loss as to why this one out of three dns servers is returning the wrong ip.
It seems like the DNS server has something set that states overwrite the returned IP address if the site being looked up is one a 5 sites. Yes, we have 5 sites that all return the same IP address. Everything else appears fine. That is why it seems like there is an override switch somewhere for lack of a better term to use.
I would also add that using any of the web based NSLOOKUP tools returns the correct value. That just seems to scream there is something wierd about this one particualr DNS server.