Using DHCP on WVD VMs with DNS scavenging enabled

If you want to use DHCP on WVD VMs with DNS scavenging enabled, please refer to the information below,

When implementing the bring your own DNS on Azure we need to turn off DNS Scavenging in order to prevent the accidental deletion of DNS records as mentioned under the "Name resolution that uses your own DNS server" section of the article Name resolution for resources in Azure virtual networks | Microsoft Docs and pasted below,

If forwarding queries to Azure doesn't suit your needs, you should provide your own DNS solution. Your DNS solution needs to:

• Provide appropriate host name resolution, via DDNS, for example. If you are using DDNS, you might need to disable DNS record scavenging. Azure DHCP leases are long, and scavenging might remove DNS records prematurely.
• Provide appropriate recursive resolution to allow resolution of external domain names.
• Be accessible (TCP and UDP on port 53) from the clients it serves, and be able to access the internet.
• Be secured against access from the internet, to mitigate threats posed by external agents.

Note: For best performance, when you are using Azure VMs as DNS servers, IPv6 should be disabled.

Assigning static IPs to the VMs in Azure Virtual Desktop Host pools is the recommended and widely adopted practice under the given scenario where you wanted to keep DNS record scavenging enabled.