Yukio Seki

Should I create Records A for Hyper-V cluster nodes?


I created two node Hyper-V cluster using Microsoft Hyper-V Server 2016 OS. There is a external switch with access to corporate LAN.

I’ve got a problem with this switch. When I set option "Register This Connections Address" for virtual network adapters (vEthernet (VS-E1)) for this switch on these two nodes, this settings change value to False. So after some time records
for this network adapters are removed by DNS server because cluster doesn’t refresh this option.

Is it default Settings for cluster?

Hostname InterfaceAlias           RegisterThisConnectionsAddress      UseSuffixWhenRegistering

HVC1N1 vEthernet (VS-E1)        False                                             

HVC1N2 vEthernet (VS-E1)        False                                             

Kind Regards Tomasz

Read full post . . . .

DNS (host A) registration of Hyper-V cluster dissapered all the time


I’ve got Hyper-V (MS Hyper-V server 2016) cluster  with two nodes.

DNS nodes names: (IP:, (IP:

DNS cluster name: (IP:

Cluster do not refresh it’s own (Host A) registration in DNS. So DNS server delete registration.  The IP settings of virtual netowrk adapters used by nodes are:

ComputerName IfAlias Status    SkipAsSource   IPv4Address                  IPv4DefaultGateway DNSServer
THVC1N1      vEthernet (VS-E1) False              {}                      
THVC1N2      vEthernet (VS-E1) {False, True}  {,}                  {,}

"SkipAsSource" parameter for cluster IP address is True .

Is it ok?

What is wrong?

Should I create DNS Host A registration for cluster name manually?

Kind Regards Tomasz

Read full post . . . .

Go Que Newsroom Categories

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 20 bytes) in /home/content/36/8658336/html/goquecom/wp-includes/taxonomy.php on line 3363