SOLVED

Problems with DNS Replication after upgrade

Copper Contributor

I created a new A/D Server 2022 to replace my A/D Server 2012.  The install completed and the FSMO roles transferred fine.  However, I cannot manage the A/D GPO.   In looking at the logs, it appears that DNS cannot replicate.   

 

Password hash synchronization failed for domain: mrc.net, domain controller hostname: MIDSRVR01.mrc.net, domain controller IP address: 172.16.1.43. Details:
Microsoft.Online.PasswordSynchronization.SynchronizationManagerException: Unable to open connection to domain: mrc.net. Error: There was an error establishing a connection to the directory replication service. Domain controller hostname: MIDSRVR01.mrc.net, domain controller IP address: 192.168.99.12 ---> Microsoft.Online.PasswordSynchronization.DirectoryReplicationServices.DrsCommunicationException: There was an error establishing a connection to the directory replication service. Domain controller hostname: MIDSRVR01.mrc.net, domain controller IP address: 192.168.99.12 ---> Microsoft.Online.PasswordSynchronization.DirectoryReplicationServices.DrsException: There was an error creating the connection context. ---> Microsoft.Online.PasswordSynchronization.DirectoryReplicationServices.DrsCommunicationException: RPC Error 1722 : The RPC server is unavailable. Error creating the RPC binding handle

 

The original A/D Server 2012 is multi-honed and it appears DNS is trying to use an IP Address on a private segment 192.168.99.12 which isn't available to the new Server.  The new server is on segment 172.16.1.x. 

 

If I look at DNS, the server IP addresses appears in this order.  How an I make the 172.16.1.43 the primary address?

 

Mikeg0210_0-1717773333903.png

 

How can I change the IP address to point to the other segment?

2 Replies
best response confirmed by Mikeg0210 (Copper Contributor)
Solution

@Mikeg0210 
Did you check on the new server if you have netlogon and sysvol ?
If thing is right you should check the DNS configuration via dns manager 

L_Youtell_974_3-1717800041065.png

Right clic on your DNS zone and select properties. On the box "Properties" select the the tab "Name Servers "  and delete the wrong IP adresse and "clic" on add to put the right IP adresse. On the box "Edit Name Server Record"  put the right IP adress and everything should be alright.

Thanks for the tip. I now only see the DNS entries for the associated segment. I assume it is successful as I can see SYSVOL replicated on both A/D servers.
1 best response

Accepted Solutions
best response confirmed by Mikeg0210 (Copper Contributor)
Solution

@Mikeg0210 
Did you check on the new server if you have netlogon and sysvol ?
If thing is right you should check the DNS configuration via dns manager 

L_Youtell_974_3-1717800041065.png

Right clic on your DNS zone and select properties. On the box "Properties" select the the tab "Name Servers "  and delete the wrong IP adresse and "clic" on add to put the right IP adresse. On the box "Edit Name Server Record"  put the right IP adress and everything should be alright.

View solution in original post