Solved DNS fails on Server 2003 domain

August 11, 2012 at 07:27:18
Specs: SERVER 2003 SP1
Please help I have been trying to resolve with no luck. When I first encountered this server when I would launch the DNS console nothing would load red x etc. Now I am at least able to launch but DNS fails. I have tried uninstalling and reinstalling no luck here is my dcdiag:

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>dcdiag /test:dns

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site\DENTALSERVER
Starting test: Connectivity
The host 784e224e-f525-4e38-b513-e908cea7b6e6._msdcs.Geager.Dentistry.c
om could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(784e224e-f525-4e38-b513-e908cea7b6e6._msdcs.Geager.Dentistry.com)
couldn't be resolved, the server name
(dentalserver.Geager.Dentistry.com) resolved to the IP address
(192.168.1.100) and was pingable. Check that the IP address is
registered correctly with the DNS server.
......................... DENTALSERVER failed test Connectivity

Doing primary tests

Testing server: Default-First-Site\DENTALSERVER

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

Running partition tests on : TAPI3Directory

Running partition tests on : ForestDnsZones

Running partition tests on : DomainDnsZones

Running partition tests on : Schema

Running partition tests on : Configuration

Running partition tests on : Geager

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

DC: dentalserver.Geager.Dentistry.com
Domain: Geager.Dentistry.com


TEST: Basic (Basc)
Error: No LDAP connectivity
Warning: adapter [00000001] Intel(R) PRO/1000 CT Network Conne
ction has invalid DNS server: 192.168.1.100 (<name unavailable>)
Warning: adapter [00000001] Intel(R) PRO/1000 CT Network Conne
ction has invalid DNS server: 192.168.1.1 (<name unavailable>)
Error: all DNS servers are invalid
Error: The A record for this DC was not found
Warning: The Active Directory zone on this DC/DNS server was n
ot found (probably a misconfiguration)

TEST: Forwarders/Root hints (Forw)
Error: Forwarders list has invalid forwarder: 192.168.1.1 (<na
me unavailable>)
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: h.root-se
rvers.net. (128.63.2.53)
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. (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)
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: 192.168.1.1 (<name unavailable>)
2 test failures on this DNS server
Name resolution is not functional. _ldap._tcp.Geager.Dentistry.co
m. failed on the DNS server 192.168.1.1

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

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: 192.168.1.100 (<name unavailable>)
1 test failure on this DNS server
Name resolution is not functional. _ldap._tcp.Geager.Dentistry.co
m. failed on the DNS server 192.168.1.100

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.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.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.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: 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: 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: 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

Summary of DNS test results:

Auth Basc Forw Del Dyn RReg Ext
________________________________________________________________
Domain: Geager.Dentistry.com
dentalserver PASS FAIL FAIL n/a PASS FAIL n/a

......................... Geager.Dentistry.com failed test DNS



See More: DNS fails on Server 2003 domain

Report •

✔ Best Answer
August 14, 2012 at 06:54:50
actually guys this issue got resolved. I needed to delete and recreate my forward lookup zone in my case certain folders in the dns console were not auto populating following a crash i just had to keep trying to re add and run dcdiag /fix and netdiag/fix eventually all was well thanks for the help guys


#1
August 11, 2012 at 09:06:49
Processor : x86 Family 15 Model 3 Stepping 4, GenuineIntel
List of installed hotfixes :
KB2079403
KB2115168
KB2229593
KB2296011
KB2345886
KB2347290
KB2360937
KB2378111
KB2387149
KB2393802
KB2412687
KB2419635
KB2423089
KB2440591
KB2443105
KB2467659
KB2476490
KB2478953
KB2478960
KB2478971
KB2483185
KB2485663
KB2506212
KB2507618
KB2507938
KB2508429
KB2509553
KB2510531-IE8
KB2510587
KB2535512
KB2536276-v2
KB2544521
KB2544521-IE8
KB2544893-v2
KB2564958
KB2566454
KB2570947
KB2572069
KB2584146
KB2585542
KB2598479
KB2603381
KB2604078
KB2618444-IE8
KB2618451
KB2620712
KB2621146
KB2621440
KB2624667
KB2631813
KB2633171
KB2633952-v2
KB2638806
KB2641653
KB2641690-v2
KB2644615
KB2645640
KB2646524
KB2647516-IE8
KB2647518
KB2653956
KB2655992
KB2656358
KB2656376
KB2656376-v2
KB2659262
KB2675157
KB2675157-IE8
KB2676562
KB2685939
KB2686509
KB2691442
KB2695962
KB2698365
KB2699988-IE8
KB2707511
KB2709162
KB2718523
KB2718704
KB2719985
KB923561
KB925398_WMP64
KB925902-v2
KB926122
KB927891
KB929123
KB932168
KB933854
KB935966
KB936357
KB941569
KB944653
KB946026
KB948496
KB950762
KB950974
KB952004
KB952069
KB952954
KB954155
KB954550-v5
KB955759
KB956572
KB956802
KB956844
KB958469
KB958644
KB959426
KB960803
KB960859
KB961118
KB961501
KB967723
KB968389
KB969059
KB970430
KB971029
KB971032
KB971657
KB972270
KB973507
KB973540
KB973815
KB973825
KB973869
KB973904
KB974112
KB974318
KB974392
KB974571
KB975025
KB975467
KB975558_WM8
KB975560
KB975713
KB977816
KB977914
KB978338
KB978542
KB978695
KB978706
KB979309
KB979482
KB979687
KB979907
KB980232
KB981322
KB982132
KB982381-IE8
KB982632-IE8
Q147222


Netcard queries test . . . . . . . : Passed

Per interface results:

Adapter : Intel Pro 1000 CT Gigabit Ethernet Adapter - Onboard

Netcard queries test . . . : Passed

Host Name. . . . . . . . . : dentalserver
IP Address . . . . . . . . : 192.168.1.100
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 192.168.1.1
Primary WINS Server. . . . : 192.168.1.100
Secondary WINS Server. . . : 192.168.1.1
Dns Servers. . . . . . . . : 192.168.1.100
192.168.1.1


AutoConfiguration results. . . . . . : Passed

Default gateway test . . . : Passed

NetBT name test. . . . . . : Passed
[WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenge
r Service', <20> 'WINS' names is missing.
No remote names have been found.

WINS service test. . . . . : Failed
The test failed. We were unable to query the WINS servers.


Global results:


Domain membership test . . . . . . : Passed


NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{E49E1740-0A7E-4988-ACF5-9777FA361F87}
1 NetBt transport currently configured.


Autonet address test . . . . . . . : Passed


IP loopback ping test. . . . . . . : Passed


Default gateway test . . . . . . . : Passed


NetBT name test. . . . . . . . . . : Passed
[WARNING] You don't have a single interface with the <00> 'WorkStation Servi
ce', <03> 'Messenger Service', <20> 'WINS' names defined.


Winsock test . . . . . . . . . . . : Passed


DNS test . . . . . . . . . . . . . : Failed
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.pdc._msdcs.Geager.Dentistry.c
om. re-registeration on DNS server '192.168.1.100' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.gc._msdcs.Geager.Dentistry.co
m. re-registeration on DNS server '192.168.1.100' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site._sites.gc.
_msdcs.Geager.Dentistry.com. re-registeration on DNS server '192.168.1.100' fail
ed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.1b6bb5a5-99d4-4286-849d-3f5af
c7b6f3b.domains._msdcs.Geager.Dentistry.com. re-registeration on DNS server '192
.168.1.100' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry gc._msdcs.Geager.Dentistry.com. re-regis
teration on DNS server '192.168.1.100' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry 784e224e-f525-4e38-b513-e908cea7b6e6._ms
dcs.Geager.Dentistry.com. re-registeration on DNS server '192.168.1.100' failed.

DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _kerberos._tcp.dc._msdcs.Geager.Dentistr
y.com. re-registeration on DNS server '192.168.1.100' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _kerberos._tcp.Default-First-Site._sites
.dc._msdcs.Geager.Dentistry.com. re-registeration on DNS server '192.168.1.100'
failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.dc._msdcs.Geager.Dentistry.co
m. re-registeration on DNS server '192.168.1.100' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site._sites.dc.
_msdcs.Geager.Dentistry.com. re-registeration on DNS server '192.168.1.100' fail
ed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Fix Failed: netdiag failed to re-register missing DNS entries for th
is DC on DNS server '192.168.1.100'.
[FATAL] No DNS servers have the DNS records for this DC registered.


Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{E49E1740-0A7E-4988-ACF5-9777FA361F87}
The redir is bound to 1 NetBt transport.

List of NetBt transports currently bound to the browser
NetBT_Tcpip_{E49E1740-0A7E-4988-ACF5-9777FA361F87}
The browser is bound to 1 NetBt transport.


DC discovery test. . . . . . . . . : Passed


DC list test . . . . . . . . . . . : Passed


Trust relationship test. . . . . . : Skipped


Kerberos test. . . . . . . . . . . : Passed


LDAP test. . . . . . . . . . . . . : Passed


Bindings test. . . . . . . . . . . : Passed


WAN configuration test . . . . . . : Skipped
No active remote access connections.


Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Skipped

Note: run "netsh ipsec dynamic show /?" for more detailed information


The command completed successfully

C:\Documents and Settings\Administrator>


Report •

#2
August 13, 2012 at 07:58:21
Something could be listening on the ports that the DNS service uses. I ran into this issue where BES and DNS were on the same server and BES would take some ports that DNS used. Run netstat /a /b and see if any other programs are listening on port 53.

--
Andrew Leonard
BL Technical Services
IT Support Maryland


Report •

#3
August 13, 2012 at 11:44:27
post the result of a ipconfig /all from the dns server for review

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

Related Solutions

#4
August 14, 2012 at 06:54:50
✔ Best Answer
actually guys this issue got resolved. I needed to delete and recreate my forward lookup zone in my case certain folders in the dns console were not auto populating following a crash i just had to keep trying to re add and run dcdiag /fix and netdiag/fix eventually all was well thanks for the help guys

Report •

#5
August 14, 2012 at 07:47:19
Thanks for coming back and posting your resolution. This may help someone else with a similar issue in the future.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

Ask Question