Register com error updating zone records
ID=6425C A DNS server on a Read-Only Domain Controller (RODC) can be authoritative for zones that are replicated to the RODC and can resolve queries for clients that use the RODC as their DNS server.Of course, a key characteristic of an RODC is that it cannot make changes to Active Directory, so resource records cannot be added manually to the zone on an RODC, and dynamic updates are not accepted from clients.
Ace Fekay MCT, MVP, MCITP EA, Exchange 2010 Enterprise Administrator, MCTS Windows 2008, Exchange 2010 & Exchange 2007, MCSE 2003/2000, MCSA Messaging 2003Microsoft Certified Trainer Microsoft MVP: Directory Services Compiled 12/7/2011 Appendix A: RODC Technical Reference Topics: from: Microsoft Official Curriculum MOC 6425C, “Configuring and Troubleshooting Windows Server 2008 Active Directory Domain Services” Module 11, page 11-31:
If all the DNS records are in place and the site still is unreachable, it’s possible that the DNS changes are propagating.
Typically only a few hours is needed for this, but it technically can take up to 24 hours to 48 hours for a DNS change to fully propagate globally.
If the selected entry is a Windows Server 2003, it will return a failure (since Server 2003 doesn’t understand RSO) and an event to be logged on the RODC.
Therefore, if there are no 2008 or newer RWDCs in the NS list, and the RODC chooses a 2003 DC, then the RODC will generate an Event 4015 when it tries to perform the RSO operation with a DNS server that runs Windows Server 2003.
It’s important to note any time a change is made to a DNS record, regardless of whether it’s adding a new record or changing the value of an existing one, it can take up to that 24 hours to 48 hours before the change is visible worldwide.