Hi All,
I am having a strange problem with my DNS on my PDC in an Active Directory Domain. I am not able to resolve any internet addresses from the PDC. All internal addresses work fine. This server has been working fine for about 2 years until yesterday when DNS just stopped working on this server. DNS works perfectly on the BDC. Here is my setup. Active Directory with 2 Domain Controllers, PDC(the system in question) and BDC. I am running Active Directory Integrated DNS on both domain controllers. I am using OpenDNS forwarders 208.67.220.220 and 208.67.222.222 and recursion. I have run dcdiag on my PDC and all tests pass. When I run dcdiag /test:dns the the forwarding test fails on both servers:
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\PD
C
Starting test: Connectivity
......................... PDC passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\PD
C
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 : mydomain
Running enterprise tests on : mydomain.local
Starting test: DNS
Test results for domain controllers:
DC: PDC.mydomain.local
Domain: mydomain.local
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. (128.9.0.107)
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: m.root-servers.net. (202.12.27.33)
TEST: Dynamic update (Dyn)
Warning: Dynamic update is enabled on the zone but not secure apg.local.
Summary of test results for DNS servers used by the above domain controllers:
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
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.9.0.107 (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 128.9.0.107
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: 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.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.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.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.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: 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: 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: 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: 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
Summary of DNS test results:
Auth Basc Forw Del Dyn RReg Ext
__________________________
__________
__________
__________
________
Domain: mydomain.local
CHIP PASS PASS FAIL PASS WARN PASS n/a
......................... mydomain.local failed test DNS
I have checked my DNS and the proper reverse zone are in DNS. I am recieving these errors in the event log:
Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 4521
Date: 7/28/2008
Time: 11:10:35 PM
User: N/A
Computer: PDC
Description:
The description for Event ID ( 4521 ) in Source ( DNS ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: 32, opendns.com.
Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1058
Date: 7/28/2008
Time: 10:21:14 PM
User: NT AUTHORITY\SYSTEM
Computer: PDC
Description:
Windows cannot access the file gpt.ini for GPO CN={31B2F340-016D-11D2-945
F-00C04FB9
84F9},CN=P
olicies,CN
=System,DC
=apg,DC=lo
cal. The file must be present at the location <\\apg.local\sysvol\apg.lo
cal\Polici
es\{31B2F3
40-016D-11
D2-945F-00
C04FB984F9
}\gpt.ini>
. (Access is denied. ). Group Policy processing aborted.
Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1030
Date: 7/28/2008
Time: 10:21:14 PM
User: NT AUTHORITY\SYSTEM
Computer: PDC
Description:
Windows cannot query for the list of Group Policy objects. Check the event log for possible messages previously logged by the policy engine that describes the reason for this.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
I ran dfsutil /PurgeMupCache to fix this error. and the DNS came back for a short time and then same DNS errors came back but the event log entries went away.
Am I missing something here?
What do you think I should do to remedy the problem? My PDC is a VMWare virtual machine and I back it up nightly, I could restore from backup. But I don't want this to happen again if it is a lingering problem from before my oldest backup. I could reinstall DNS. I could also promote my BDC to PDC and demote my PDC to BDC delete it and reinstall as BDC.
What do you think?
Thanks,
Jerick70
Start Free Trial
