Resolve “Hyper-V failed to enable reverse replication” error

One of our client has Hyper-V servers and makes use of the Hyper-V replication technology for redundancy. Recently it was noticed that error pops up on enabling reverse replication while executing planned failover of virtual machines. The VM failover completed to the Hyper-V replica server with the below error


The VM is now online in the Hyper-V replica server and in shutdown state in the Hyper-V primary server [new replica server]. If you try to right click on the VM on the replica server [new Primary Server] and select Replication Menu, you can see the option Reverse Replication. Trying to enable reverse replication from here will also result in the above error.


As suggested by online articles, tried to find the following registry key ‘HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\DnsClient\DnsPolicyConfig to check if Name Resolution Policy was enabled or not, but I was unable to locate the same.




Hence tried the below steps suggested by Technet article

  • Launched Local Group Policy Editor (Gpedit.msc)
  • Under Local Computer Policy navigated to Computer Configuration -> Windows Settings -> Name Resolution Policy
  • In Create Rules section, select FQDN from the drop down menu and specify the replica host server FQDN
  • Select the Encoding tab and Enable Encoding
  • From the drop down, select UTF-8 with Mapping and select Create rule


All the rules will be listed in the Name Resolution Policy Table. You can use the PowerShell command ‘netsh namespace show effectivepolicy‘ to view the configured rules in the Name Resolution Policy Table.


However, the issue still persisted. Taking a closer look on the error it was found that the Replica server name in the error was not correct. It was in the format ‘servername.domain‘ instead of the correct FQDN of the server which is ‘servername.domain.local‘.

This occurred because when you configure Reverse Replication, by default it tries to configure the Replica server name in the ‘servername.domain‘ format. The issue was resolved on modifying the replica server name and reverse replication worked like a charm.


Reference :