ConvergeTech deploys custom DNS server VMs inside a spoke VNet and wants Azure VM agents and DHCP clients to receive the proper DNS suffix and resolver behavior. Which DHCP option and Azure recursive resolver IP should they configure/forward to ensure Azure-internal name resolution still works and clients get the correct domain suffix?

Setting DHCP option 15 to the desired DNS suffix (e.g., corp.converge.local) ensures that client VMs automatically append this suffix when resolving unqualified hostnames. Configuring the custom DNS servers to forward unresolved queries to Azure's recursive resolver at 168.63.129.16 is crucial for Azure-internal name resolution (e.g., for PaaS services or other VMs in the same VNet). This hybrid approach allows custom domain resolution while maintaining Azure's native name resolution capabilities. Incorrect options: Setting DHCP option 15 to 127.0.0.1 is incorrect as this is the loopback address and not a valid DNS suffix. Using 8.8.8.8 as the recursive resolver would bypass Azure's internal resolution. Manually setting option 6 on every VM is not scalable or practical, and 10.0.0.4 is an arbitrary IP, not Azure's recursive resolver. Setting option 15 to a hostname is not a valid use for a DNS suffix, and disabling forwarding to Azure would break Azure-internal name resolution.