Azim Ali
asked on
DNS error 4015
We have 2 DC. DNS is installed in both. Now both DC are giving this error: The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The extended error debug information (which may be empty) is "". The event data contains the error.
Ran DNS Test, Below is the result:
C:\Windows\system32>dcdiag /test:dns
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
Home Server = QAKSQSDCDN01P
* Identified AD Forest.
Done gathering initial info.
Doing initial required tests
Testing server: QADN\QAKSQSDCDN01P
Starting test: Connectivity
......................... QAKSQSDCDN01P passed test Connectivity
Doing primary tests
Testing server: QADN\QAKSQSDCDN01P
Starting test: DNS
DNS Tests are running and not hung. Please wait a few minutes...
......................... QAKSQSDCDN01P passed test DNS
Running partition tests on : DomainDnsZones
Running partition tests on : KI
Running partition tests on : ForestDnsZones
Running partition tests on : Schema
Running partition tests on : Configuration
Running enterprise tests on : KEPPELGROUP.COM
Starting test: DNS
Test results for domain controllers:
DC: QAKSQSDCDN01P.KI.KEPPELGRO UP.COM
Domain: KI.KEPPELGROUP.COM
TEST: Basic (Basc)
Warning: adapter [00000010] Microsoft Hyper-V Network Adapter
has invalid DNS server: 10.4.234.16 (QAKSQSDCDN01P)
Warning: adapter [00000010] Microsoft Hyper-V Network Adapter
has invalid DNS server: 10.4.246.16 (QAKSQSDCDA01P)
Warning: adapter [00000010] Microsoft Hyper-V Network Adapter
has invalid DNS server: 127.0.0.1 (QAKSQSDCDN01P)
Error: all DNS servers are invalid
TEST: Dynamic update (Dyn)
Warning: Failed to delete the test record dcdiag-test-record i
n zone KI.KEPPELGROUP.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: 10.4.234.16 (QAKSQSDCDN01P)
2 test failure on this DNS server
Name resolution is not functional. _ldap._tcp.KEPPELGROUP.COM . fa
iled on the DNS server 10.4.234.16
DNS server: 10.4.246.16 (QAKSQSDCDA01P)
1 test failure on this DNS server
Name resolution is not functional. _ldap._tcp.KEPPELGROUP.COM . fa
iled on the DNS server 10.4.246.16
DNS server: 8.8.4.4 (<name unavailable>)
1 test failure on this DNS server
Name resolution is not functional. _ldap._tcp.KEPPELGROUP.COM . fa
iled on the DNS server 8.8.4.4
DNS server: 8.8.8.8 (<name unavailable>)
1 test failure on this DNS server
Name resolution is not functional. _ldap._tcp.KEPPELGROUP.COM . fa
iled on the DNS server 8.8.8.8
Summary of DNS test results:
Auth Basc Forw Del Dyn RReg Ext
__________________________ __________ __________ __________ _________
Domain: KI.KEPPELGROUP.COM
QAKSQSDCDN01P PASS FAIL PASS PASS WARN FAIL n/a
......................... KEPPELGROUP.COM failed test DNS
C:\Windows\system32>
Ran DNS Test, Below is the result:
C:\Windows\system32>dcdiag
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
Home Server = QAKSQSDCDN01P
* Identified AD Forest.
Done gathering initial info.
Doing initial required tests
Testing server: QADN\QAKSQSDCDN01P
Starting test: Connectivity
......................... QAKSQSDCDN01P passed test Connectivity
Doing primary tests
Testing server: QADN\QAKSQSDCDN01P
Starting test: DNS
DNS Tests are running and not hung. Please wait a few minutes...
......................... QAKSQSDCDN01P passed test DNS
Running partition tests on : DomainDnsZones
Running partition tests on : KI
Running partition tests on : ForestDnsZones
Running partition tests on : Schema
Running partition tests on : Configuration
Running enterprise tests on : KEPPELGROUP.COM
Starting test: DNS
Test results for domain controllers:
DC: QAKSQSDCDN01P.KI.KEPPELGRO
Domain: KI.KEPPELGROUP.COM
TEST: Basic (Basc)
Warning: adapter [00000010] Microsoft Hyper-V Network Adapter
has invalid DNS server: 10.4.234.16 (QAKSQSDCDN01P)
Warning: adapter [00000010] Microsoft Hyper-V Network Adapter
has invalid DNS server: 10.4.246.16 (QAKSQSDCDA01P)
Warning: adapter [00000010] Microsoft Hyper-V Network Adapter
has invalid DNS server: 127.0.0.1 (QAKSQSDCDN01P)
Error: all DNS servers are invalid
TEST: Dynamic update (Dyn)
Warning: Failed to delete the test record dcdiag-test-record i
n zone KI.KEPPELGROUP.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: 10.4.234.16 (QAKSQSDCDN01P)
2 test failure on this DNS server
Name resolution is not functional. _ldap._tcp.KEPPELGROUP.COM
iled on the DNS server 10.4.234.16
DNS server: 10.4.246.16 (QAKSQSDCDA01P)
1 test failure on this DNS server
Name resolution is not functional. _ldap._tcp.KEPPELGROUP.COM
iled on the DNS server 10.4.246.16
DNS server: 8.8.4.4 (<name unavailable>)
1 test failure on this DNS server
Name resolution is not functional. _ldap._tcp.KEPPELGROUP.COM
iled on the DNS server 8.8.4.4
DNS server: 8.8.8.8 (<name unavailable>)
1 test failure on this DNS server
Name resolution is not functional. _ldap._tcp.KEPPELGROUP.COM
iled on the DNS server 8.8.8.8
Summary of DNS test results:
Auth Basc Forw Del Dyn RReg Ext
__________________________
Domain: KI.KEPPELGROUP.COM
QAKSQSDCDN01P PASS FAIL PASS PASS WARN FAIL n/a
......................... KEPPELGROUP.COM failed test DNS
C:\Windows\system32>
i have added our local ip as dns and as per the log you can see its not only the 8.8.8.8 ip which is giving error , it also gives error for my local ip which is 10.4.234.16 , event 4015 is created every 5 minutes , Not sure what else to do
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
no more information provided
Google does not know a thing about your internal servers.
you just need to have your internal DNS as: 127.0.0.1 or local IP.
and use the Forwarders of DNS to anywhere you want (google,comcast,etc)