Expert Gary Olsen gives you guidance on how to fix the problem or avoid it entirely.Occasionally these zones become corrupt or in some cases, they disappear.
![]()
Recreate Primary Active Directory Integrated Dns Zone How To Fix TheYou decide to convert to an ADI primary configuration, so you go to the DC hosting the standard primary zone, (DC1 in London) and select the option to make the zone Active Directory Integrated. At that point, all the DNS records will be moved to the AD database (as shown in Figure 2) and replicated to the other DCs. The DCs, which also are DNS servers hosting secondary copies of the zone from the initial configuration, now have both copies. As long as they arent rebooted, they will resolve names using the secondary zone. However, when they are rebooted, they will see both -- and have to make a choice either to use the secondary or the ADI primary version of the zone. Thus, after booting, when you open up the DNS snap-in, you will notice that the secondary zone is gone, but the ADI Primary version of the zone is there. Figure 3 shows the DNS structure after you have converted to ADI primary on DC1 London and rebooted DC3 and DC4 in Denver and Boston respectively. Note that DC3 and DC4 have ADI Primary zones while DC2 in Seattle still has the standard secondary at least until it is rebooted. ADI zones present the same challenge all multi-master replication applications have -- trying to get it fixed while the bad stuff is still getting replicated. If you have an ADI zone that is corrupt -- that is, records disappear or updates dont work or name resolution doesnt work and it seems to be configured correctly, or zones disappear off of DNS servers -- then the best way to get control is to convert it back to a standard primary and start over. For sake of argument, lets say its DC1 in our example. Delete the Bogus.com zone from DC2, DC3 and DC4. Warning If you go to the DNS snap-in and delete an ADI zone, it will warn you that if you continue, it will delete the zone from the AD. This is not good Do not delete the zone using the DNS Snap-in.) Delete the zone in this manner. Recreate Primary Active Directory Integrated Dns Zone Install DNS FromThis action will uninstall DNS from that server and remove the DCs copy of the zone file as you would view it in the snap-in. Repeat this for all DCs EXCEPT DC1. Now you have a single writeable source of the zone. Make any DNS repairs needed (missing host records, delegations and so on). On DC2, 3, 4 and SRV1, create standard secondary zones. Let it simmer for a couple of days. Make sure that the problems that led you to believe the zone was corrupt do not appear. At this point, you are done. If you want to convert it back to an ADI zone, do the following. The reboot (as we noted earlier) will convert the secondary zone back to ADI primary. If you dont want to reboot, just delete the standard secondary zone on these servers and add bogus.com as an ADI primary zone. He authored Windows 2000: Active Directory Design and Deployment and co-authored Windows Server 2003 on HP ProLiant Servers. Learn the challenges youll need to overcome with these insights on. RIGHT OUTER JOIN techniques and find various examples for creating SQL.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |