I have the following: Server A -- W2k3 with AD/ DHCP/DNS First DC
Server B -- W2k3 with AD (just added for redudancy)
All looks good so far. I decided to add DNS to Server B for redundancy as well. Everything appears to have populated except my Forward lookup zone records. All that shows is Server B. I created the zone using the wizard. It is an AD Integrated Primary. I also received some errors in Server B's DNS events. The most recent warning is:
The zone mydomain.net was previously loaded from the directory partition MicrosoftDNS but another copy of the zone has been found in directory partition DomainDnsZones.mydomain.net. The DNS Server will ignore this new copy of the zone. Please resolve this conflict as soon as possible.
If an administrator has moved this zone from one directory partition to another this may be a harmless transient condition. In this case, no action is necessary. The deletion of the original copy of the zone should soon replicate to this server.
If there are two copies of this zone in two different directory partitions but this is not a transient caused by a zone move operation then one of these copies should be deleted as soon as possible to resolve this conflict.
To change the replication scope of an application directory partition containing DNS zones and for more details on storing DNS zones in the application directory partitions, please see Help and Support.
Any ideas? Should I have not created the zone on the second machine?