I am trying a POC to have high available standalone DFS namespace server. For this, I have configured, 2 VM’s on Azure with a shared premium disk and provisioned a cluster. Both the VM’s are on-prem domain joined through Express Route.
The Ip address of both the VM’s lie in the same subnet(x.x.x.45. and x.x.x.47). I have used windows server 2019 so cluster uses distributed server name and takes the Ip address of the active VM in the cluster. When I configure the DFS Namespace Server Role on this cluster, it provisions a Server (Network Name); dfs-test is the name in my case. I assign a static Ip address to this server name (dfs-test) and the Ip address(x.x.x.44) also belongs to the same subnet. However, I see corresponding to this action inside VM, a network interface is created in the Azure and it is not attached to any machine. Also, I see that a computer object is created in AD for dfs-test as well an entry in DNS is created in corp DNS server for dfs-test pointing to x.x.x.44. The issue is I want to access this location on network \\dfs-test (\\x.x.x.4) which is not happening. I am anticipating since this IP address is not assigned to any machine, it is not routed anywhere. The ping test also fails from other machines in the same domain. Any idea, what is the missing configuration here which allows me to access this DFS role (dfs-test) with Ip address x.x.x.44 over the network.

