DC registration in DNS

  • Thread starter Thread starter Jason Gray
  • Start date Start date
J

Jason Gray

I've recently been working on a win2k adv. server sp4
running an AD DC. There was a host of issues that I was
able to resolve, however, the last problem that I cannot
seem to fix is a DNS registration problem with the DC.

I'm able to find the A record using nslookup:
set q=srv
2ccbbabc-104e-40e7-8562-203e25946dc2._msdcs.bardel
Click to expand...

Server: bd2.bardel
Address: 192.168.1.9

2ccbbabc-104e-40e7-8562-203e25946dc2._msdcs.bardel
canonical name = bd2.bardel

However, when I do a netdiag I get:
------------
DNS test.............................: Failed
[WARNING] The DNS entries for the DC are not registered
correctly on the DNS server '192.168.1.9'. Please wait
for 30 minutes for DNS server replication.
[FATAL] No DNS servers have the DNS records for this DC
registered.

-------------

The domain is a single label and so I've add the
AllowSingleLabelDnsDomain registery value into the
Netlogon Parameters key but this has not resolved the
problem.

There is a Child domain as well (bdc.bardel) that runs
well and all the replication services are functioning
normally. I have setup a secondary DNS for the BARDEL
zone on the child domain as well as a AD integrated zone
BDC. I've run dcdiag on the child domain:
dcdiag /test:registerindns /dnsdomain:bdc.bardel
Click to expand...

and get a pass.

However when I run the same command on the BARDEL domain:
dcdiag /test:registerindns /dnsdomain:bardel
Click to expand...

I do not get a pass. It reports:

bdc2 failed test RegisterInDns.

I've manually register the entries from the netlogon.dns
file into the DNS zone, restarted both the DNS and
netlogon services and rebooted the system.

I've added the necessary gc._msdcs, _ldap and Alias
entries necessary for the DNS to register the DC. I've
read multiple newsgroup entries but cannot find the
solution to this very annoying problem.

Any thoughts would be great.

Cheers,

Jason
 
Verify that the "Register this connections address in DNS" option is checked
for the NIC of your system.
If multihomed you may want to check the box on all NICs.
Jason Gray said:
I've recently been working on a win2k adv. server sp4
running an AD DC. There was a host of issues that I was
able to resolve, however, the last problem that I cannot
seem to fix is a DNS registration problem with the DC.

I'm able to find the A record using nslookup:
set q=srv
2ccbbabc-104e-40e7-8562-203e25946dc2._msdcs.bardel
Click to expand...

Server: bd2.bardel
Address: 192.168.1.9

2ccbbabc-104e-40e7-8562-203e25946dc2._msdcs.bardel
canonical name = bd2.bardel

However, when I do a netdiag I get:
------------
DNS test.............................: Failed
[WARNING] The DNS entries for the DC are not registered
correctly on the DNS server '192.168.1.9'. Please wait
for 30 minutes for DNS server replication.
[FATAL] No DNS servers have the DNS records for this DC
registered.

-------------

The domain is a single label and so I've add the
AllowSingleLabelDnsDomain registery value into the
Netlogon Parameters key but this has not resolved the
problem.

There is a Child domain as well (bdc.bardel) that runs
well and all the replication services are functioning
normally. I have setup a secondary DNS for the BARDEL
zone on the child domain as well as a AD integrated zone
BDC. I've run dcdiag on the child domain:
dcdiag /test:registerindns /dnsdomain:bdc.bardel
Click to expand...

and get a pass.

However when I run the same command on the BARDEL domain:
dcdiag /test:registerindns /dnsdomain:bardel
Click to expand...

I do not get a pass. It reports:

bdc2 failed test RegisterInDns.

I've manually register the entries from the netlogon.dns
file into the DNS zone, restarted both the DNS and
netlogon services and rebooted the system.

I've added the necessary gc._msdcs, _ldap and Alias
entries necessary for the DNS to register the DC. I've
read multiple newsgroup entries but cannot find the
solution to this very annoying problem.

Any thoughts would be great.

Cheers,

Jason
Click to expand...
 
Curtis,

I found the prblem was in my manual entries in the DNS. I
used the nslookup.dns file to create the entries in the
zone file. Once I re-checked these values and ran netdiag
the DNS error went away.

That being said, I did check the "Register this connection
in DNS" box and re-ran the netdiag command and received a
slightly different error:

[WARNING] Cannot find a primary authoritative DNS
serverfor the name 'bd2.bardel.' [RCODE_SERVER_FAILURE]
The name 'bd2.bardel.' may not be registered in DNS.

I don't see how this error can occur. The DNS has both
the A and PTR records for the Host and NS entries. When I
run netdiag without the "Register this connection..."
option the error disappears.

However, I still get an error when I run the
dcdiag /test:regsiterindns command. The error is still
the same. How can one test say that the DC in registered
but another says it is not?

Cheers,

Jason
-----Original Message-----
Verify that the "Register this connections address in DNS" option is checked
for the NIC of your system.
If multihomed you may want to check the box on all NICs.
Jason Gray said:
I've recently been working on a win2k adv. server sp4
running an AD DC. There was a host of issues that I was
able to resolve, however, the last problem that I cannot
seem to fix is a DNS registration problem with the DC.

I'm able to find the A record using nslookup:
set q=srv
2ccbbabc-104e-40e7-8562-203e25946dc2._msdcs.bardel
Click to expand...

Server: bd2.bardel
Address: 192.168.1.9

2ccbbabc-104e-40e7-8562-203e25946dc2._msdcs.bardel
canonical name = bd2.bardel

However, when I do a netdiag I get:
------------
DNS test.............................: Failed
[WARNING] The DNS entries for the DC are not registered
correctly on the DNS server '192.168.1.9'. Please wait
for 30 minutes for DNS server replication.
[FATAL] No DNS servers have the DNS records for this DC
registered.

-------------

The domain is a single label and so I've add the
AllowSingleLabelDnsDomain registery value into the
Netlogon Parameters key but this has not resolved the
problem.

There is a Child domain as well (bdc.bardel) that runs
well and all the replication services are functioning
normally. I have setup a secondary DNS for the BARDEL
zone on the child domain as well as a AD integrated zone
BDC. I've run dcdiag on the child domain:
dcdiag /test:registerindns /dnsdomain:bdc.bardel
Click to expand...

and get a pass.

However when I run the same command on the BARDEL domain:
dcdiag /test:registerindns /dnsdomain:bardel
Click to expand...

I do not get a pass. It reports:

bdc2 failed test RegisterInDns.

I've manually register the entries from the netlogon.dns
file into the DNS zone, restarted both the DNS and
netlogon services and rebooted the system.

I've added the necessary gc._msdcs, _ldap and Alias
entries necessary for the DNS to register the DC. I've
read multiple newsgroup entries but cannot find the
solution to this very annoying problem.

Any thoughts would be great.

Cheers,

Jason
Click to expand...


.
Click to expand...
 
Back
Top