Read Only Domain Controllers and DNS zone updates

Posted by Mike M on Server Fault See other posts from Server Fault or by Mike M
Published on 2009-12-02T20:25:52Z Indexed on 2010/03/12 1:07 UTC
Read the original article Hit count: 468

I have a Windows 2003 domain and just added a new DC that runs 2008 R2. I updated the schema accordingly for both forest and domain levels. I also made sure to run /rodcprep at the time I did this. I have a branch office with a 2008 R2 file/print server that is a read-only domain controller (DC).

The one problem I have been having is with AD-integrated DNS records updates. In the data center, we had to make an IP address change on a particular server. All our other sites' DCs (2003) updated the record fine. The 2008 R2 DC in the data center also updates its record fine. However, the RODC in the branch office does not.

So if I nslookup the target server on a 2003 DC, the IP address is correct. Same with the 2008 R2 DC in the data center. But an nslookup on the branch office RODC still pulls in the old IP address.

Moreover, any new records we've created (e.g., just added a new terminal server) do not get updated on the branch RODC either.

Is there something simple I'm missing? How do I get the RODC to sync its AD-integrated DNS records with the rest of my world?

Thank you in advance for your responses.

Mike

© Server Fault or respective owner

Related posts about dns

Related posts about windows-server-2008-r2