Reg-Azure static IP 168.63.129.16

Robin Hitch 105 Reputation points
2024-03-11T09:25:35.5933333+00:00

In Azure Vnet when we add the custom DNS, does virtual machine in that Vnet can we resolve name resolution to Azure resources ? or we need to add th Azure DNS IP address (168.63.129.16) in the Vnet DNS server.

And if no needed then is there any situation we need to add the 168.63.129.16 IP address to the Vnet Custom DNS server ?User's image

Azure DNS
Azure DNS
An Azure service that enables hosting Domain Name System (DNS) domains in Azure.
597 questions
0 comments No comments
{count} votes

Accepted answer
  1. ChaitanyaNaykodi-MSFT 23,021 Reputation points Microsoft Employee
    2024-03-16T01:06:39.73+00:00

    @Robin Hitch

    Thank you for reaching out.I understand you have a question regarding Azure IP address 168.63.129.16 Azure DNS IP.

    The IP address 168.63.129.16 is owned by Microsoft and is the default DNS of azure services. By this I mean if you set the default DNS option above, then the DNS resolution happens using this IP address i.e it enables communication with the DNS virtual server. Now when you keep default option then you can resolve the VM's deployed in the same virtual network using <vmName>.internal.cloudapp.net to their private IP address. This domain is internal to Azure and cannot be changed. This is actually very well explained in John Savill's video here (4:00 - 10.11)

    Based on your question above

    In Azure Vnet when we add the custom DNS, does virtual machine in that Vnet can we resolve name resolution to Azure resources ?

    This depends actually on if you have custom DNS server deployed in your VNET which can resolve the resources with their own custom domain names. For this you have create zones and manage records for all the resources.

    And if no needed then is there any situation we need to add the 168.63.129.16 IP address to the Vnet Custom DNS server ?

    No, I do not think there will be a scenario where you will need to add the 168.63.129.16 IP address to the Vnet Custom DNS server, as this is the default option.

    Hope this helps! Thank you!


    ​​Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Luca Lionetti 2,966 Reputation points
    2024-03-11T09:41:03.9966667+00:00

    Hi,

    Welcome to Microsoft Q&A community forum!

    If you use your own dns you can forward all the azure queries to azure resovers.

    DNS servers within a virtual network can forward DNS queries to the recursive resolvers in Azure. This procedure enables you to resolve host names within that virtual network. For example, a domain controller (DC) running in Azure can respond to DNS queries for its domains, and forward all other queries to Azure. Forwarding queries allows VMs to see both your on-premises resources (via the DC) and Azure-provided host names (via the forwarder). Access to the recursive resolvers in Azure is provided via the virtual IP 168.63.129.16.

    Ref link

    https://learn.microsoft.com/en-us/azure/virtual-network/virtual-networks-name-resolution-for-vms-and-role-instances?tabs=redhat#name-resolution-that-uses-your-own-dns-server

    Hope this helps

    Cheers

    Luca

    Please "Accept as Answer" and Upvote if the answer provided is useful, so that you can help others in the community looking for remediation for similar issues