Solved

DCDiag errors

Posted on 2007-11-29
5
1,197 Views
Last Modified: 2008-05-31
What do I do about this??? It was working fine yesterday.


C:\Program Files\Support Tools>dcdiag /s:stantonmainbdc /test:dns

Domain Controller Diagnosis

Performing initial setup:
   Done gathering initial info.

Doing initial required tests

   Testing server: NewYork\STANTONMAINBDC
      Starting test: Connectivity
         ......................... STANTONMAINBDC passed test Connectivity

Doing primary tests

   Testing server: NewYork\STANTONMAINBDC

DNS Tests are running and not hung. Please wait a few minutes...

   Running partition tests on : ForestDnsZones

   Running partition tests on : DomainDnsZones

   Running partition tests on : Schema

   Running partition tests on : Configuration

   Running partition tests on : stantoncarpet

   Running enterprise tests on : stantoncarpet.com
      Starting test: DNS
         Test results for domain controllers:

            DC: stantonmainbdc.stantoncarpet.com
            Domain: stantoncarpet.com


               TEST: Basic (Basc)
                  Warning: adapter [00000001] 3Com EtherLink XL 10/100 PCI TX NI
C (3C905B-TX) has invalid DNS server: 64.115.0.9 (<name unavailable>)
                  Warning: adapter [00000001] 3Com EtherLink XL 10/100 PCI TX NI
C (3C905B-TX) has invalid DNS server: 64.115.0.10 (<name unavailable>)

               TEST: Forwarders/Root hints (Forw)
                  Error: Root hints list has invalid root hint server: a.root-se
rvers.net. (198.41.0.4)
                  Error: Root hints list has invalid root hint server: b.root-se
rvers.net. (192.228.79.201)
                  Error: Root hints list has invalid root hint server: c.root-se
rvers.net. (192.33.4.12)
                  Error: Root hints list has invalid root hint server: d.root-se
rvers.net. (128.8.10.90)
                  Error: Root hints list has invalid root hint server: e.root-se
rvers.net. (192.203.230.10)
                  Error: Root hints list has invalid root hint server: f.root-se
rvers.net. (192.5.5.241)
                  Error: Root hints list has invalid root hint server: g.root-se
rvers.net. (192.112.36.4)
                  Error: Root hints list has invalid root hint server: h.root-se
rvers.net. (128.63.2.53)
                  Error: Root hints list has invalid root hint server: i.root-se
rvers.net. (192.36.148.17)
                  Error: Root hints list has invalid root hint server: j.root-se
rvers.net. (192.58.128.30)
                  Error: Root hints list has invalid root hint server: k.root-se
rvers.net. (193.0.14.129)
                  Error: Root hints list has invalid root hint server: l.root-se
rvers.net. (198.32.64.12)
                  Error: Root hints list has invalid root hint server: l.root-se
rvers.net. (199.7.83.42)
                  Error: Root hints list has invalid root hint server: m.root-se
rvers.net. (202.12.27.33)

               TEST: Records registration (RReg)
                  Network Adapter [00000001] 3Com EtherLink XL 10/100 PCI TX NIC
 (3C905B-TX):
                     Error: Missing A record at DNS server 64.115.0.9 :
                     stantonmainbdc.stantoncarpet.com

                     Error: Missing CNAME record at DNS server 64.115.0.9 :
                     92f7ab21-3b51-4875-bf7b-93190307d70c._msdcs.stantoncarpet.c
om

                     Error: Missing DC SRV record at DNS server 64.115.0.9 :
                     _ldap._tcp.dc._msdcs.stantoncarpet.com

                     Error: Missing GC SRV record at DNS server 64.115.0.9 :
                     _ldap._tcp.gc._msdcs.stantoncarpet.com

                     Error: Missing PDC SRV record at DNS server 64.115.0.9 :
                     _ldap._tcp.pdc._msdcs.stantoncarpet.com

                     Error: Missing A record at DNS server 64.115.0.10 :
                     stantonmainbdc.stantoncarpet.com

                     Error: Missing CNAME record at DNS server 64.115.0.10 :
                     92f7ab21-3b51-4875-bf7b-93190307d70c._msdcs.stantoncarpet.c
om

                     Error: Missing DC SRV record at DNS server 64.115.0.10 :
                     _ldap._tcp.dc._msdcs.stantoncarpet.com

                     Error: Missing GC SRV record at DNS server 64.115.0.10 :
                     _ldap._tcp.gc._msdcs.stantoncarpet.com

                     Error: Missing PDC SRV record at DNS server 64.115.0.10 :
                     _ldap._tcp.pdc._msdcs.stantoncarpet.com

               Error: Record registrations cannot be found for all the network a
dapters

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

            DNS server: 64.115.0.9 (<name unavailable>)
               1 test failure on this DNS server
               Name resolution is not functional. _ldap._tcp.stantoncarpet.com.
failed on the DNS server 64.115.0.9

            DNS server: 64.115.0.10 (<name unavailable>)
               1 test failure on this DNS server
               Name resolution is not functional. _ldap._tcp.stantoncarpet.com.
failed on the DNS server 64.115.0.10

            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.12
7.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.12
7.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.12
7.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.12
7.in-addr.arpa. failed on the DNS server 198.32.64.12

            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.12
7.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.12
7.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.12
7.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.12
7.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.12
7.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.12
7.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.12
7.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.12
7.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.12
7.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.12
7.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: stantoncarpet.com
               stantonmainbdc               PASS WARN FAIL PASS PASS FAIL n/a

         ......................... stantoncarpet.com failed test DNS

C:\Program Files\Support Tools>
0
Comment
Question by:Vegas16Lax
  • 3
  • 2
5 Comments
 
LVL 2

Assisted Solution

by:theric76
theric76 earned 125 total points
ID: 20373261
Hi Vegas16Lax,
could you post an ipconfig /all run on your server?
It seems like you are using 64.115.0.9 and 64.115.0.10 as DNS servers on your server TCP/IP properties. Did you have to change anything?

0
 

Author Comment

by:Vegas16Lax
ID: 20373414
Windows IP Configuration

   Host Name . . . . . . . . . . . . : stantonmain
   Primary Dns Suffix  . . . . . . . : stantoncarpet.com
   Node Type . . . . . . . . . . . . : Unknown
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : stantoncarpet.com

Ethernet adapter Local Area Connection 2:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Broadcom BCM5708S NetXtreme II GigE (NDIS
 VBD Client) #2
   Physical Address. . . . . . . . . : 00-1A-64-89-5E-B6
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 192.168.110.71
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.110.6
   DNS Servers . . . . . . . . . . . : 192.168.110.7
                                       192.168.110.3
                                       192.168.120.5
0
 

Author Comment

by:Vegas16Lax
ID: 20373497
It is only happening on this dns server. There are two other dns servers in our site and when I run dcdiag on them, they report clean results.
0
 

Author Comment

by:Vegas16Lax
ID: 20374373
I cleaned up a few things. But, the only real change I made was adding two Forwarders to my ISP's dns servers and now it works. Why would this particular server need forwarders and the others don't??? All three are DC's running DNS active-directory integrated/secure only.
0
 
LVL 2

Accepted Solution

by:
theric76 earned 125 total points
ID: 20374605
I guess you have two NICs on that server.
The first NIC is 3Com EtherLink XL 10/100 PCI TX NIC (3C905B-TX) and, as I can read from DCDIAG results, it's using 64.115.0.9 and 64.115.0.10 as DNS servers.

The second NIC is Broadcom BCM5708S NetXtreme II GigE, showing in ipconfig output. This configuration seems to be ok.

In any case, I guess you should remove DNS servers from the first NIC settings, but it would be useful if you could give some informations about the services you are using on that particular server

0

Featured Post

Is Your AD Toolbox Looking More Like a Toybox?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Learn about cloud computing and its benefits for small business owners.
Is your Office 365 signature not working the way you want it to? Are signature updates taking up too much of your time? Let's run through the most common problems that an IT administrator can encounter when dealing with Office 365 email signatures.
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 …
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …

832 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