WORKAROUND:
Assuming you have AD-Integrated DNS, then before you run the project; manually configure the Network Interface on each DC to use ONE DC from that domain as its Preferred DNS server.
For example: if I add DC1, DC2 and DC3 from the same domain to my ADVL project, then I should modify the Network Interface on all 3 to use the target IP address of DC1 as their preferred DNS server. Similarly if I have ChildDC1, ChildDC2 and ChildDC3, I should modify the Network interface on all 3 to use the target IP address of ChildDC1 as their preferred DNS server.
If you have already run the project, then you need to revise the Preferred DNS server settings as explained above, and you must also correct the DNS Delegations on the root Domain:
- Open DNS Manager on a Root DC in the target network
- Expand the root domain’s forward lookup zone
- Right click on a delegation and go to Properties
- On the Name Servers tab: Remove any DC that was not part of your ADVL Project
- Edit the remaining DC(s) to use the target IP address assigned to them in the ADVL project
- Repeat steps 3-5 for each delegation in the zone
After making these changes, click “retry last operation” on each of your child DCs. If that fails, or if you’ve already closed the ADVL console then you can either wait for replication or force it using AD Sites and Services or command line utilities like repadmin.exe.
STATUS:
The following defects have been identified and will be addressed in an upcoming 10.1 maintenance release:
- RMADFE-3250 - ADVL automatic DNS selection doesn't work if no target item has preferred DNS
- RMADFE-870 - Remove DNS records for computer that was not included in ADVL project