Windows Server

Gilbert · Guest

I have 6 domain controllers and 2 of them run the DNS service with Active
directory integrated zones. I am getting replication errors because the DNS
is not functioning properly. I ran DCDIAG /test:dns and here's what i get:
(same failed test connectivity for all 6 servers, I just didn't list them all)

also, I get event ids 4013 and 4015 under DNS and 2087 and 2088 under
directory service.

Performing initial setup:
[GSDT1] Directory Binding Error 6:
The handle is invalid.
This may limit some of the tests that can be performed.
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\GSDT1
Starting test: Connectivity
[GSDT1] DsBindWithSpnEx() failed with error 6,
The handle is invalid..
......................... GSDT1 failed test Connectivity

Testing server: Default-First-Site-Name\GSD01
Starting test: Connectivity
[GSD01] DsBindWithSpnEx() failed with error 6,
The handle is invalid..
......................... GSD01 failed test Connectivity

Test results for domain controllers:

TEST: Basic (Basc)
Error: No DS RPC connectivity

TEST: Forwarders/Root hints (Forw)
Error: Forwarders list has invalid forwarder: 172.16.0.2
(<name unavailable>)
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. (192.228.79.201)
Error: Root hints list has invalid root hint server:
c.root-servers.net. (192.33.4.12)

TEST: Authentication (Auth)
Error: Authentication failed with specified credentials

TEST: Basic (Basc)
Error: No DS RPC connectivity
Error: No WMI connectivity

Summary of test results for DNS servers used by the above domain controllers:

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

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

Summary of DNS test results:

Auth Basc Forw Del Dyn RReg
Ext

________________________________________________________________
GSDT1 PASS FAIL FAIL PASS PASS PASS n/a
GSD01 FAIL FAIL n/a n/a n/a n/a
n/a
ges1 PASS FAIL n/a n/a n/a n/a
n/a
GSDT2 PASS FAIL n/a n/a n/a n/a
n/a
gsdweb PASS FAIL n/a n/a n/a n/a
n/a
gmst1 PASS FAIL n/a n/a n/a n/a
n/a

jmhsuton@nooter.com · Guest

How do you have your system setup? Is it with secondary zones are are you
using active directory integrated? Also it shows that you have an invalid
forwarder? If yoiu remove the forwarders and just use root hints that might
help. Some how you need to be able to post a diagram of how your system is
laid out.

"Gilbert" wrote:

Gilbert · Guest

only Active Directory integrated zones. I did notice that the _msdcs zone is
missing from the Forward lookup zones. I have 2 servers running DNS. One of
the servers is missing the _msdcs zone and the other server says it can't
connect to itself when I launch the DNS console. (therefore I can't see
anything, just a red X on the server itself)

How do I get the _msdcs zone back??

If you read the error message, it also says the root hints are invalid. I
think if I can get my _msdcs zone back, it will fix a lot of the errors.

"jmhsuton@nooter.com" wrote:

Gilbert · Guest

I got the DNS errors fixed by doing this:
I manually re-created the zone, then ran NETDIAG /FIX and that repopulated
the zone. I then ran NET STOP NETLOGON, and then NET START NETLOGON to
re-register all the domain controllers in that zone. Then it wouldn't
replicate due to trust issues. So I ran nltest /sc_reset:example.com
(where example.com is the domain name)

Then I ran repadmin /bind and then repadmin /syncall to replicate all the
domain controllers.

That fixed that issue by now I have a RPC error which I'll post in a
different section of the forums.

"Gilbert" wrote:

	Windows Server Forum Index -> DNS	All times are GMT
Page 1 of 1