If we have custom DNS in the virtual network and the same vNet is linked with the private DNS, Then the VM (DNS :network interface inherited from vnet ) will resolve to both DNS zone ?

@Robin Hitch Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well. I understand that you would like to know what happens in case of a custom DNS server and Private DNS Zone. Per your verbatim, you have A VNET/NIC Configured to use a custom DNS Server The same VNET is linked to a Private DNS Zone Please let me know if my understanding is incorrect. In this case, the former takes precedence. DNS requests from the VMs in the VNET would only go to the custom DNS server. This means, DNS names of the network interface would not be resolved. Thanks, Kapil Please Accept an answer if correct. Original posters help the community find answers faster by identifying the correct answer.

If we have custom DNS in the virtual network and the same vNet is linked with the private DNS, Then the VM with resolve to both DNS zone ?

Accepted answer

KapilAnanth-MSFT 39,451 Reputation points Microsoft Employee

2023-12-19T10:51:49.6033333+00:00
@Robin Hitch

Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.

I understand that you would like to know what happens in case of a custom DNS server and Private DNS Zone.

Per your verbatim, you have

A VNET/NIC Configured to use a custom DNS Server

The same VNET is linked to a Private DNS Zone

Please let me know if my understanding is incorrect.

In this case, the former takes precedence.

DNS requests from the VMs in the VNET would only go to the custom DNS server.

This means, DNS names of the network interface would not be resolved.

Thanks,

Kapil

Please Accept an answer if correct.

Original posters help the community find answers faster by identifying the correct answer.
Please sign in to rate this answer.

1 person found this answer helpful.
Robin Hitch 105 Reputation points

2023-12-19T11:01:02.31+00:00

Hi @KapilAnanth-MSFT

Thank for your response, and yes that's my query.

And if custom DNS serve is not resolved, will it be resolved with private DNS zone ?

KapilAnanth-MSFT 39,451 Reputation points Microsoft Employee

2023-12-19T11:16:09.2133333+00:00

@Robin Hitch ,

You can specify the list of DNS servers you would like to use and Azure VNET will follow the order of DNS servers in the list you provide.

It's important to verify that you list your DNS servers in the correct order for your environment. DNS servers are used in the order that they're specified in the list. They don't work as a round-robin setup. If the first DNS server in the list can be reached, the client uses that DNS server, regardless of whether the DNS server is functioning properly.

Refer : DNS servers of a virtual network

You can have upto 20 such DNS servers per VNET.

Refer : Azure VNET Limits

Now, if you are interested in failing back to Azure Provided DNS in case your custom DNS servers all fail, you can do so as below:

Add the Azure Wireserver IP as the last custom DNS

What is IP address 168.63.129.16?

IP address 168.63.129.16 is a virtual public IP address that is used to facilitate a communication channel to Azure platform resources. One of it's purpose is to enable communication with the DNS virtual server to provide filtered name resolution to the resources (such as VM) that don't have a custom DNS server. This filtering makes sure that customers can resolve only the hostnames of their resources

Thanks,

Kapil

Please Accept an answer if correct.

Original posters help the community find answers faster by identifying the correct answer.

Robin Hitch 105 Reputation points

2023-12-19T11:27:47.03+00:00

Thanks @KapilAnanth-MSFT
Sign in to comment

Share via

If we have custom DNS in the virtual network and the same vNet is linked with the private DNS, Then the VM with resolve to both DNS zone ?

0 additional answers