Azure VM won't pick up custom DNS settings

Question

_{Thursday, February 1, 2018 3:45 PM}

Hey guys, I'm deploying AAD (DNS) for the first time but I just can't get my Azure VM to pick up the new DNS servers via DHCP.  I've tried setting custom DNS servers in the RG01-vnet and the VM's NIC, I've restarted the server, but it's still using the default Azure VM forwarded.  I've tried looking for documentation and all I can find it "just specify the custom DNS and reboot your VMs are you're done."

Also, I've confirmed that both AAD DNS servers are online, pingable, and are answering DNS queries if I manually specify them within nslookup.  This appears to be just a DHCP issue since the VM isn't picking up the DNS servers via DHCP.

Please help!

All replies (6)

_{Friday, February 2, 2018 4:25 PM ✅Answered}

thanks for the response Phil, could you re-attempt a reboot using Azure CLI with the bellow command: 

Non-domain-joined Windows clients attempt unsecured Dynamic DNS (DDNS) updates when they boot or when their IP address changes. I suspect the IP lease wasn’t expired in the first reboot, could you give it one more try and check again Phil ?

_{Thursday, February 1, 2018 6:19 PM}

Thanks for reaching out Phil, I wanted to check, is the VM already domain joined ? if it's not yet, this doc provides more details:/en-us/azure/active-directory-domain-services/active-directory-ds-admin-guide-join-windows-vm-portal 

Also, could you double check if the Network config is not statically set on that VM ? Here's a full doc on DNS config via AAD: [https://docs.microsoft.com/en-us/azure/active-directory-domain-services/active-directory-ds-admin-guide-administer-dns

L](https://docs.microsoft.com/en-us/azure/active-directory-domain-services/active-directory-ds-admin-guide-administer-dns)et me know if this helps.

_{Thursday, February 1, 2018 9:54 PM}

No, the VM is not already joined.  It doesn't know how to reach AAD DNS so it can't resolve the _ldap._tcp.dc._msdcs.dentonsolutions.com SRV record.  Once that resolves I think I'll be good to go.

The network config is NOT statically set on that VM.  (I hear that's a big "no no" in Azure) It's set to DHCP but even after setting my custom DNS servers in two places (network and NIC) it's still using the default Azure forwarder.

What next?

_{Thursday, February 1, 2018 10:31 PM}

 I see, Let's check the following, have you updated the DNS settings per task 4 here ?

Also did you reboot the VM from within ?  if so, try the bellow option:
Virtual machines in the network only get the new DNS settings after a restart. If you need them to get the updated DNS settings right away, trigger a restart either by the portal, PowerShell, or the CLI.

Let me know if any of the suggested points work. 

Thanks, 

_{Friday, February 2, 2018 5:39 AM}

Yes like I said before I did all that and it's not working.  I have only rebooted the server by going to the server within the Azure dashboard and clicking Restart though.  If I should reboot with another method please let me know.

Phil

_{Tuesday, February 6, 2018 3:18 PM | 1 vote}

That worked.  Thanks Adam!