Having a strange issue with Azure vm's and pvs (particularly server 2025). Occasionally, the target devices will not get dns information from the vnet, resulting in a lack of domain connectivity. if using 'custom dns on the nic of the target device, it works consistently.

We have seen this as well. Custom DNS to your domain controlled dns is preferrable.

well thats going to be a pita 😉

You get set it on the subnet itself, then the dhcp for azure delivers your dns instead of their dns

on the subnet or vnet? I thought you could only do it on the vnet or the nic. we currently have it set up on the vnet as 'custom' but thats where i see the problem occurring.

You are correct. vnet. So on my small azure lab I have my on-prem dns servers on the vnet, and when I bring up my opnsense vpn to link azure to onprem all my windows machines just resolve locally.

just an update to this: Microsoft is still taking their time analyzing things. For now, my workaround is a bat file that runs on startup to flushdns, ipconfig /renew, gpupdate /force