Allow custom DNS search domain for virtual networks
Thanks for recently adding the ability to specify custom DNS servers for virtual networks.
I assume this is implemented with DHCP.
We are unfortunately not able to rely on this feature yet because we also set a custom DNS domain search.
This can be done with DHCP option 119, and this is how we have our non-Azure LAN configured.
Azure DNS support for private zones is now in limited preview and custom DNS suffix will be part of that. See http://aka.ms/azureprivatedns for details of the feature.
Jack Chen commented
https://docs.microsoft.com/en-ca/azure/dns/private-dns-overview doesn't seem support custom search domain yet?
I searched "suffix" in the document and it only show in lines related with Reverse DNS.
This feature gets more meaningful and important when it comes to VNet peering.
Currently hosts in VNet still receive DNS suffix via DHCP like rxswwfbgpbpuhmmafhobadrtsc.lx.internal.cloudapp.net which is specific to each VNet they connect to. So there's no easy way for hosts to resolve names of peer hosts in other VNets.
Using DNS private zones linked to all of VNets and this custom DNS suffix feature will make it much simper.