asked on

DCDiag errors

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>

SOLUTION

theric76

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Vegas16Lax

ASKER

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

Vegas16Lax

ASKER

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.

Vegas16Lax

ASKER

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.

ASKER CERTIFIED SOLUTION

theric76

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial