Windows Server 2008
--
Questions
--
Followers
Top Experts
dcdiag /test:dns fails
Hello,
I'm trying to repair the DNS on a Windows 2008 R2 Server that fails the command dcdiag /test:dns. How can I reset or repair this? Here is the following test results:
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
Home Server = LINFORD01
* Identified AD Forest.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\LI
Starting test: Connectivity
The host 09db5bef-5e6e-4260-9da7-63
not be resolved to an IP address. Check the DNS server, DHCP, server
name, etc.
......................... LINFORD01 failed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\LI
Starting test: DNS
DNS Tests are running and not hung. Please wait a few minutes...
......................... LINFORD01 passed test DNS
Running partition tests on : ForestDnsZones
Running partition tests on : DomainDnsZones
Running partition tests on : Schema
Running partition tests on : Configuration
Running partition tests on : linford
Running enterprise tests on : linford.com
Starting test: DNS
Test results for domain controllers:
DC: LINFORD01.linford.com
Domain: linford.com
TEST: Basic (Basc)
Error: No LDAP connectivity
Warning: adapter
[00000006] Broadcom NetXtreme Gigabit Ethernet has invalid
DNS server: 192.168.1.11 (LINFORD01)
Warning: adapter
[00000006] Broadcom NetXtreme Gigabit Ethernet has invalid
DNS server: 127.0.0.1 (LINFORD01)
Error: all DNS servers are invalid
No host records (A or AAAA) were found for this DC
Warning: The Active Directory zone on this DC/DNS server was
not found (probably a misconfiguration)
TEST: Dynamic update (Dyn)
Warning: Failed to add the test record _dcdiag_test_record in zone linford.com
TEST: Records registration (RReg)
Error: Record registrations cannot be found for all the network
adapters
Summary of test results for DNS servers used by the above domain
controllers:
DNS server: 192.168.1.11 (LINFORD01)
2 test failure on this DNS server
Name resolution is not functional. _ldap._tcp.linford.com. failed on the DNS server 192.168.1.11
Summary of DNS test results:
Auth Basc Forw Del Dyn RReg Ext
__________________________
Domain: linford.com
LINFORD01 PASS FAIL PASS n/a WARN FAIL n/a
......................... linford.com failed test DNS
I'm trying to repair the DNS on a Windows 2008 R2 Server that fails the command dcdiag /test:dns. How can I reset or repair this? Here is the following test results:
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
Home Server = LINFORD01
* Identified AD Forest.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\LI
Starting test: Connectivity
The host 09db5bef-5e6e-4260-9da7-63
not be resolved to an IP address. Check the DNS server, DHCP, server
name, etc.
......................... LINFORD01 failed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\LI
Starting test: DNS
DNS Tests are running and not hung. Please wait a few minutes...
......................... LINFORD01 passed test DNS
Running partition tests on : ForestDnsZones
Running partition tests on : DomainDnsZones
Running partition tests on : Schema
Running partition tests on : Configuration
Running partition tests on : linford
Running enterprise tests on : linford.com
Starting test: DNS
Test results for domain controllers:
DC: LINFORD01.linford.com
Domain: linford.com
TEST: Basic (Basc)
Error: No LDAP connectivity
Warning: adapter
[00000006] Broadcom NetXtreme Gigabit Ethernet has invalid
DNS server: 192.168.1.11 (LINFORD01)
Warning: adapter
[00000006] Broadcom NetXtreme Gigabit Ethernet has invalid
DNS server: 127.0.0.1 (LINFORD01)
Error: all DNS servers are invalid
No host records (A or AAAA) were found for this DC
Warning: The Active Directory zone on this DC/DNS server was
not found (probably a misconfiguration)
TEST: Dynamic update (Dyn)
Warning: Failed to add the test record _dcdiag_test_record in zone linford.com
TEST: Records registration (RReg)
Error: Record registrations cannot be found for all the network
adapters
Summary of test results for DNS servers used by the above domain
controllers:
DNS server: 192.168.1.11 (LINFORD01)
2 test failure on this DNS server
Name resolution is not functional. _ldap._tcp.linford.com. failed on the DNS server 192.168.1.11
Summary of DNS test results:
Auth Basc Forw Del Dyn RReg Ext
__________________________
Domain: linford.com
LINFORD01 PASS FAIL PASS n/a WARN FAIL n/a
......................... linford.com failed test DNS
Zero AI Policy
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
Is this the only DC in the domain? If so, is it pointing to itself for DNS? I see that it's pointing to 192.168.1.11, but you didn't mention whether that's the server's IP.
Is the DNS Server service running, and if you look in the DNS console, do you see forward lookup zones named linford.com and _msdcs.linford com?
Is the DNS Server service running, and if you look in the DNS console, do you see forward lookup zones named linford.com and _msdcs.linford com?
It is the only DC in the domain and it's IP is 192.168.1.11.
I've attached a screenshot.
I've attached a screenshot.
dcdiag /fix results:
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Administrator>dcd
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
Home Server = LINFORD01
* Identified AD Forest.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\LI
Starting test: Connectivity
The host 09db5bef-5e6e-4260-9da7-63
not be resolved to an IP address. Check the DNS server, DHCP, server
name, etc.
......................... LINFORD01 failed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\LI
Skipping all tests, because server LINFORD01 is not responding to
directory service requests.
Running partition tests on : ForestDnsZones
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Running partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Running partition tests on : Schema
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Running partition tests on : Configuration
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Running partition tests on : linford
Starting test: CheckSDRefDom
......................... linford passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... linford passed test CrossRefValidation
Running enterprise tests on : linford.com
Starting test: LocatorCheck
......................... linford.com passed test LocatorCheck
Starting test: Intersite
......................... linford.com passed test Intersite
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Administrator>dcd
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
Home Server = LINFORD01
* Identified AD Forest.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\LI
Starting test: Connectivity
The host 09db5bef-5e6e-4260-9da7-63
not be resolved to an IP address. Check the DNS server, DHCP, server
name, etc.
......................... LINFORD01 failed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\LI
Skipping all tests, because server LINFORD01 is not responding to
directory service requests.
Running partition tests on : ForestDnsZones
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Running partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Running partition tests on : Schema
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Running partition tests on : Configuration
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Running partition tests on : linford
Starting test: CheckSDRefDom
......................... linford passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... linford passed test CrossRefValidation
Running enterprise tests on : linford.com
Starting test: LocatorCheck
......................... linford.com passed test LocatorCheck
Starting test: Intersite
......................... linford.com passed test Intersite
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
sounds like you need to do some metadata cleanup see https://www.experts-exchange.com/questions/27457654/DNS-on-Windows-2008-deleted.html
cheers
Andrew
cheers
Andrew
I have already done that and would like information on how to reset DNS. Perhaps delete the DNS object and recreate it?.
ASKER CERTIFIED SOLUTION
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
Windows Server 2008
--
Questions
--
Followers
Top Experts
Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.