I bugged the behavior many moons ago … to my knowledge, no fix has appeared as yet.  The precise cause escapes me but IIR it was related to the ticket/token attached to the DHCP client service on the newly-born domain’s DC.  Two immediate solutions exist - 

 

1.       reboot the new DC one more time

2.       or -

a.       temporarily configure the zone to permit non-secure updates &

b.      on the new DC, run ipconfig /registerdns or restart the DHCP client

 

HTH                                                                                                                                                                                             

--
Dean Wells
MSEtechnology
* Email: [EMAIL PROTECTED]
http://msetechnology.com

 

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matheesha Weerasinghe
Sent: Sunday, July 30, 2006 3:07 PM
To: [email protected]
Subject: [ActiveDir] DNS oddities?

 

All

Can someone please explain the following observation?

Installed a new R2 DC forest with one DC/DNS.
created a new dns zone for use by a child domain (yet to be created). The zone is replicated to all domain controllers of the root domain. Enabled secure dynamic update only.
Installed a new child domain and pointed to root domain DC/DNS.

All records required were created apart from the A record for the child DC. How come it can create all records other than the "A" record?. If I delete the child donain's zone from the parent domain DC/DNS server, and recreate it, then use "netdiag /test:dns /fix" on the child DC. It does the same. Creates all records except for the "A".

I am puzzled as if the secure dynamic updates allow all these records to be created, whats up with the "A" record?

Also netdiag /test:dns on child DC reports all required everything as OK even though the "A" record is missing in the child domain zone.

Thoughts?

Cheers

M~

Reply via email to