Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.
Wrt,
As far I understand, if we are specifying custom DNS servers in Vnets then even Azure PaaS related private DNS zone resolution (let's say for Blob or File etc.) will be redirected to the custom DNS servers bypassing Azure DNS, then I will have to setup conditional forwarders to be able to resolve them. Is my understanding correct?
- Yes
- This is correct.
Your requirement :
Now, what if I want my both of the setup work together, i.e. I want my Vnets to refer to my custom DNS servers as well as I want PaaS services resolutions to be redirected to Azure DNS.
Wrt,
Can this be achieved if I specify '168.63.129.16' as a custom DNS server in the Vnet? Apologies if this sound non-sensical/ silly but just wanted to clarify my doubt.
- It is technically possible to define '168.63.129.16' as a custom DNS server in the VNet.
- This will work but not as you expect.
- It is because, as you mentioned, there is a order of precedence in the custom DNS servers specified in the VNet.
- The order is the DNS servers specified in the VNET DNS configuration page.
- See : DNS servers of a virtual network
- What this means is that as long as the first DNS server is reachable, Azure will continue to use it even if it gives wrong or null response to the DNS Query.
Kindly let us know if this helps or you need further assistance on this issue.
Thanks,
Kapil
Please don’t forget to close the thread by clicking "Accept the answer" wherever the information provided helps you, as this can be beneficial to other community members.