I'm having trouble after migrating a primary dns zone to active directory
Before: private namespace is mycompany.local
DC1 - W2K SP4 - DNS (primary) - DHCP - all FSMO roles
DC2 - W2K SP4 - DNS (secondary) - DHCP (different scope from DC1)
No errors in DNS eventlog.
--> I upgraded mycompany.local zone to active directory integrated to get
benefists of multimaster replication:
everything went fine on DC1, so I had a fresh copy of text dns file
transformed into systemMicrosoftDNSmycompany.local branch of AD.
--> I forced AD replication in AD Sites And Services to DC2.
Still good, but DNS on DC2 was still saying "secondary" as its own
--> I ended up to change secondary zone to active dir integrated on 2nd DC
(I know, this is nonsense), and DNS Mgmt Tool prompted "a zone
mycompany.local already exist in AD, what you want to do: delete zone in AD
and populate with source or take existing": I opted for the second choice.
Panic: zone mycompany.local disappeared
from DC2; after restarting DNS on
DC1, even the first one was gone(!)
Panic2: what can I do?
I restored text file and create zone as before (primary on DC1 and secondary
0) everything works fine (DHCP, name resolution, recursion, forwarding, ecc)
1) records still exist in AD;
2) I rebooted DC2 and once again zone mycompany.local was gone; I recreated
the zone as secondary and "tranfer from master" works;
3) I'm scared of rebooting DC1.
After all, can I still make a clean reliable DDNS implementation of
mycompany.local in both servers?
AD Integrated would be preferred. Article Q294328 was not so clear to me.
I Need help.
Thank you in advance