test failure on this DNS server

I current have a windows 2003 domain of which I am planning to implement and update to windows 2012r2... I wanted to make sure dns was healthy so I ran a dcdiag /v /c /d /e on my main domain controller.. I have 5 ad servers...it failed.. at the end of the output you see this:
 dc2k3ad1                     PASS PASS FAIL PASS PASS PASS n/a  
 dc2kdns                       PASS PASS FAIL PASS PASS PASS n/a  
 dc2k3ad3                     PASS PASS FAIL PASS PASS PASS n/a  
 DC2K3AD4                   PASS PASS FAIL PASS PASS PASS n/a  
 dc2k3ad2                     PASS PASS FAIL PASS PASS PASS n/a  
         
You'll notice the FAIL column. this occurs on 4 of the 5 ad servers. For whatever reason the dc2k3ad3 server does not fail when run from the ad3 server ..  

   dc2k3ad3                     PASS PASS PASS PASS PASS PASS n/a  


in the output :

Summary of test results for DNS servers used by the above domain controllers:

            DNS server: 66.28.0.61 (<name unavailable>)
               5 test failures on this DNS server
               This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 66.28.0.61
               [Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
               Total query time:0 min. 0 sec., Total WMI connection time:0 min. 2 sec.
               
            DNS server: 66.28.0.45 (<name unavailable>)
               5 test failures on this DNS server
               This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 66.28.0.45
               [Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
               Total query time:0 min. 0 sec., Total WMI connection time:0 min. 2 sec.
               
            DNS server: 202.12.27.33 (m.root-servers.net.)
               5 test failures on this DNS server
               This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 202.12.27.33
               [Error details: 9002 (Type: Win32 - Description: DNS server failure.)]
               Total query time:0 min. 0 sec., Total WMI connection time:0 min. 0 sec.
               
            DNS server: 199.7.91.13 (d.root-servers.net.)
               5 test failures on this DNS server
               This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 199.7.91.13
               [Error details: 9002 (Type: Win32 - Description: DNS server failure.)]
               Total query time:0 min. 0 sec., Total WMI connection time:0 min. 0 sec.


 On the server that passes:

Summary of test results for DNS servers used by the above domain controllers:

            DNS server: 10.18.1.20 (<name unavailable>)
               All tests passed on this DNS server
               This is a valid DNS server
               Name resolution is funtional. _ldap._tcp SRV record for the forest root domain is registered
               Total query time:0 min. 0 sec., Total WMI connection time:0 min. 0 sec.
               
            DNS server: 10.18.1.57 (<name unavailable>)
               All tests passed on this DNS server
               This is a valid DNS server
               Name resolution is funtional. _ldap._tcp SRV record for the forest root domain is registered
               Total query time:0 min. 0 sec., Total WMI connection time:0 min. 0 sec.
               
            DNS server: 10.18.1.6 (<name unavailable>)
               All tests passed on this DNS server
               This is a valid DNS server
               Name resolution is funtional. _ldap._tcp SRV record for the forest root domain is registered
               Total query time:0 min. 0 sec., Total WMI connection time:0 min. 0 sec.
               
            DNS server: 172.18.1.7 (<name unavailable>)
               All tests passed on this DNS server
               This is a valid DNS server
               Name resolution is funtional. _ldap._tcp SRV record for the forest root domain is registered
               Total query time:0 min. 0 sec., Total WMI connection time:0 min. 0 sec.
               
            DNS server: 172.19.1.29 (<name unavailable>)
               All tests passed on this DNS server
               This is a valid DNS server
               Name resolution is funtional. _ldap._tcp SRV record for the forest root domain is registered
               Total query time:0 min. 0 sec., Total WMI connection time:0 min. 0 sec.
               
            DNS server: 66.28.0.45 (<name unavailable>)
               All tests passed on this DNS server
               This is a valid DNS server
               Total query time:0 min. 0 sec., Total WMI connection time:0 min. 2 sec.
               
            DNS server: 66.28.0.61 (<name unavailable>)
               All tests passed on this DNS server
               This is a valid DNS server
               Total query time:0 min. 0 sec., Total WMI connection time:0 min. 2 sec.
               
         Summary of DNS test results:
         

         I have researched all over.. and nothing I do makes a difference...

        I even try to replace the root hints: but
 
  When I open my dns and try to repopulate my dns root hints...

  These 4 come up unknown....
k.root-servers.net
i.root-servers.net
m.root-servers.net
j.root-servers.net

but if I nslookup them individually and then they resolve...

         Has anyone run into this............
changariAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

asavenerCommented:
You will never find a PTR record for 127.0.0.1; it's the host loopback interface.

Something in your NIC configuration and/or binding order is messed up.
asavenerCommented:
Why are the failing domain controllers using public DNS servers, and the one that passed is using internal DNS servers?
David Johnson, CD, MVPOwnerCommented:
I use forwarders exclusively since I get the same errors from the root hints servers.
changariAuthor Commented:
Hello All.....

   just a quick note .. I resolved this today .. Basically all servers are setup correctly as far as I could tell.. we use forwarders .. and are setup for dns hints... I was going a bit crazy of why it worked on mly 1 AD server.. So I decided to eliminate similarities... It came to the DCDIAG.exe .. on 4 of the servers it a older 5.2.xxxx version and on the one that worked was 5.2.3790.3959.. I updated the systems tools and forwarder issues disappeared and I am now getting :

dc2k3ad1                    PASS PASS PASS PASS PASS PASS n/a
dc2kdns                      PASS PASS PASS PASS PASS PASS n/a
DC2K3AD4                 PASS PASS PASS PASS PASS PASS n/a
dc2k3ad3                    PASS PASS PASS PASS PASS PASS n/a
dc2k3ad2                    PASS PASS PASS PASS PASS PASS n/a

WHO FIGURED???????????

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
changariAuthor Commented:
the problem was resolved
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
DNS

From novice to tech pro — start learning today.