Solved

DNS diagnostic errors

Posted on 2009-05-14
2
803 Views
Last Modified: 2012-05-07
Hi
We have some schools servers
Windows 2003, Active directory and DNS server installed.
We occationally get error messages in event viewer agains DNS Server

I downloaded windows 2003 support tools to use
dcdiag to test DNS Server.
To my big supprise it looks like its totally failing.

Can anyone have a look at this result file of that test:
It says that its invalid DNS Servers. They are bouth valid DNS Servers for TDC (provider)

It also gives errors to all the root hints and I am not sure why

Our DNS Server is setup as we are using Terminal Server.

Can anyone tell me if this is serious and if this might affect the stability of our server

I am totally new to DNS and got lost trying to read about it so if anyone can find some good easy documentations or som basic analyze what I need to do, I would be a happy man

Kind Regards
Morten
Domain Controller Diagnosis
 

Performing initial setup:

   Done gathering initial info.
 

Doing initial required tests

   

   Testing server: Default-First-Site-Name\TERMINALSRV

      Starting test: Connectivity

         ......................... TERMINALSRV passed test Connectivity
 

Doing primary tests

   

   Testing server: Default-First-Site-Name\TERMINALSRV

   

   Running partition tests on : ForestDnsZones

   

   Running partition tests on : DomainDnsZones

   

   Running partition tests on : Schema

   

   Running partition tests on : Configuration

   

   Running partition tests on : domasger

   

   Running enterprise tests on : domasger.local

      Starting test: DNS

         Test results for domain controllers:

            

            DC: TERMINALSRV.domasger.local

            Domain: domasger.local
 

                  

               TEST: Basic (Basc)

                  Warning: adapter [00000009] Intel(R) PRO/100 Intelligent Server Adapter has invalid DNS server: 193.162.153.164 (<name unavailable>)

                  Warning: adapter [00000009] Intel(R) PRO/100 Intelligent Server Adapter has invalid DNS server: 194.239.134.83 (<name unavailable>)

                  

               TEST: Forwarders/Root hints (Forw)

                  Error: Root hints list has invalid root hint server: a.root-servers.net. (198.41.0.4)

                  Error: Root hints list has invalid root hint server: b.root-servers.net. (192.228.79.201)

                  Error: Root hints list has invalid root hint server: c.root-servers.net. (192.33.4.12)

                  Error: Root hints list has invalid root hint server: d.root-servers.net. (128.8.10.90)

                  Error: Root hints list has invalid root hint server: e.root-servers.net. (192.203.230.10)

                  Error: Root hints list has invalid root hint server: f.root-servers.net. (192.5.5.241)

                  Error: Root hints list has invalid root hint server: g.root-servers.net. (192.112.36.4)

                  Error: Root hints list has invalid root hint server: h.root-servers.net. (128.63.2.53)

                  Error: Root hints list has invalid root hint server: i.root-servers.net. (192.36.148.17)

                  Error: Root hints list has invalid root hint server: j.root-servers.net. (192.58.128.30)

                  Error: Root hints list has invalid root hint server: k.root-servers.net. (193.0.14.129)

                  Error: Root hints list has invalid root hint server: l.root-servers.net. (198.32.64.12)

                  Error: Root hints list has invalid root hint server: l.root-servers.net. (199.7.83.42)

                  Error: Root hints list has invalid root hint server: m.root-servers.net. (202.12.27.33)

         

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

            DNS server: 202.12.27.33 (m.root-servers.net.)

               1 test failure 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

               

            DNS server: 199.7.83.42 (l.root-servers.net.)

               1 test failure 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.83.42

               

            DNS server: 198.41.0.4 (a.root-servers.net.)

               1 test failure 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 198.41.0.4

               

            DNS server: 198.32.64.12 (l.root-servers.net.)

               1 test failure 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 198.32.64.12

               

            DNS server: 194.239.134.83 (<name unavailable>)

               1 test failure 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 194.239.134.83

               Name resolution is not functional. _ldap._tcp.domasger.local. failed on the DNS server 194.239.134.83

               

            DNS server: 193.162.153.164 (<name unavailable>)

               1 test failure 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 193.162.153.164

               Name resolution is not functional. _ldap._tcp.domasger.local. failed on the DNS server 193.162.153.164

               

            DNS server: 193.0.14.129 (k.root-servers.net.)

               1 test failure 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 193.0.14.129

               

            DNS server: 192.58.128.30 (j.root-servers.net.)

               1 test failure 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 192.58.128.30

               

            DNS server: 192.5.5.241 (f.root-servers.net.)

               1 test failure 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 192.5.5.241

               

            DNS server: 192.36.148.17 (i.root-servers.net.)

               1 test failure 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 192.36.148.17

               

            DNS server: 192.33.4.12 (c.root-servers.net.)

               1 test failure 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 192.33.4.12

               

            DNS server: 192.228.79.201 (b.root-servers.net.)

               1 test failure 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 192.228.79.201

               

            DNS server: 192.203.230.10 (e.root-servers.net.)

               1 test failure 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 192.203.230.10

               

            DNS server: 192.112.36.4 (g.root-servers.net.)

               1 test failure 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 192.112.36.4

               

            DNS server: 128.8.10.90 (d.root-servers.net.)

               1 test failure 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 128.8.10.90

               

            DNS server: 128.63.2.53 (h.root-servers.net.)

               1 test failure 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 128.63.2.53

               

         Summary of DNS test results:

         

                                            Auth Basc Forw Del  Dyn  RReg Ext  

               ________________________________________________________________

            Domain: domasger.local

               TERMINALSRV                  PASS WARN FAIL PASS PASS PASS n/a  

         

         ......................... domasger.local failed test DNS

Open in new window

0
Comment
Question by:morten444
2 Comments
 
LVL 57

Accepted Solution

by:
Mike Kline earned 500 total points
Comment Utility
Real good advice below from Chris Dent (one of the best DNS guys around) about running it with the latest version of dcdiag.  See if you get different results
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/SBS_Small_Business_Server/Q_23734770.html
So those are not all invalid, You can see an updated list here http://www.internic.net/zones/named.root
Can you right click your DNS server and go to properties then the forwarders tab  for "all other DNS domain" do you all forward out to another server?
Thanks
Mike
0
 

Author Closing Comment

by:morten444
Comment Utility
Thanks Mike.
I followed the link, read the articles and now my diag tool is running with no errors after minor alterations.  :)
0

Featured Post

Highfive + Dolby Voice = No More Audio Complaints!

Poor audio quality is one of the top reasons people don’t use video conferencing. Get the crispest, clearest audio powered by Dolby Voice in every meeting. Highfive and Dolby Voice deliver the best video conferencing and audio experience for every meeting and every room.

Join & Write a Comment

There have been a lot of times when we have seen the need to enter a large number of DNS entries in a forward lookup zone. The standard procedure would be to launch the DNS Manager console, create the Zone and start adding new hosts using the New…
Disabling the Directory Sync Service Account in Office 365 will stop directory synchronization from working.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …

728 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

14 Experts available now in Live!

Get 1:1 Help Now