Quantcast
Channel: Network Infrastructure Servers forum
Viewing all articles
Browse latest Browse all 5877

NSLOOKUP & Ping results for public domains differ between AD DNS and Public DNS

$
0
0

All servers in this are Server 2008 R2.

I’ve been searching all day for the answer to this one, but I’ve not seen something like this before. I have setup two AD servers with DNS on each (10.6.0.30, 10.6.0.31). The systems themselves have their DNS set to their local DNS servers and the DNS server is forwarding OpenDNS (208.67.222.222, 208.67.220.220). We purchased another company and with it came their own AD. I setup a secondary zone on our DNS servers for their old DNS until we are ready to migrate everyone over to our primary AD domain.

 

 I found that when I ping and run an nslookup against our local DNS servers (doesn’t matter if it’s out primary server or even the old one from the company we purchased) the results are different than when I run the same tests against OpenDNS and Google’s DNS.

 

For example:

With our local DNS servers

> financialfreedomadvisors.com

Server:  UnKnown

Address:  10.6.0.30

 

Non-authoritative answer:

financialfreedomadvisors.com    nameserver = expired2.domainsupport.net

financialfreedomadvisors.com    nameserver = expired1.domainsupport.net

 

expired2.domainsupport.net      internet address = 216.104.163.6

expired1.domainsupport.net      internet address = 216.104.162.6

 

And with OpenDNS

> server 208.67.222.222

Default Server:  resolver1.opendns.com

Address:  208.67.222.222

 

> financialfreedomadvisors.com

Server:  resolver1.opendns.com

Address:  208.67.222.222

 

Non-authoritative answer:

financialfreedomadvisors.com

        primary name server = ns.rackspace.com

        responsible mail addr = hostmaster.rackspace.com

        serial  = 1350799618

        refresh = 3600 (1 hour)

        retry  = 300 (5 mins)

        expire  = 1814400 (21 days)

        default TTL = 300 (5 mins)

financialfreedomadvisors.com    MX preference = 10, mail exchanger = MX1.EMAILSR

VR.com

financialfreedomadvisors.com    MX preference = 20, mail exchanger = MX2.EMAILSR

VR.com

financialfreedomadvisors.com    nameserver = ns2.rackspace.com

financialfreedomadvisors.com    nameserver = ns.rackspace.com

financialfreedomadvisors.com    internet address = 184.106.13.82

 

I just don’t see any reason why this would happen. I have a set of AD/DNS servers setup in the same manner in another of our offices (different domain) and the test results between both OpenDNS and those DNS server match, i.e. they are correct unlike this results I’ve show above.

I have searched all day, but I haven't found anyone who has described this exactly. There are no host file entries and there are no records which correspond to this. Most nslookups and pings resolve correctly, it's just a few of our domains which do not.


Viewing all articles
Browse latest Browse all 5877

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>