вторник, ноември 19, 2024

Azure VNET name resolving

 

VNET resolving steps

  1. If a custom DNS /Private Resolver is configured -> send all requests there
  2. If Azure DNS services (Azure Public DNS) are configured
    1. Check for a private zone attached to the vnet
    •  if yes -> answer with Private DNS RR; done
    • If no -> b.
    1. Send query to Public Azure DNS-es

That is why under Private DNS zone -> Settings -> Virtual Network Links we have to have a bound link to the Vnet

Only attached to the Private Zones VNETs will be able to resolve entries inside the zone (i.e. they are not shared outside of vnet linked resource)

If I want to use Private DNS zone with Custom DNS I have to configure <private DNS zone> forwarding ruleset on Custom DNS to 168.63.129.16.

 BIND format -> private DNS zone= example.internal

/etc/bind/named.conf.options

 

zone "example.internal" {

    type forward;

    forwarders { 168.63.129.16; };

};

 

 

https://xkln.net/blog/dns-name-resolution-in-azure/

https://learn.microsoft.com/en-us/azure/virtual-network/virtual-networks-name-resolution-for-vms-and-role-instances?tabs=redhat

https://learn.microsoft.com/en-us/azure/dns/private-dns-overview