How to Use Azure DNS Private Resolver and Outbound Endpoints

[@petersach]

This was super helpful! Thanks

[@chairborne33]

Thank you so much for this video and the one on the inbound configuration. Helped me out a bunch.

[@UmapathiMurari]

on-prem domain and private zone domain are same. Outbound resolver will resolve or VM's will to private zone thanks for your content

[@GyanSingh-oy6iu]

What if scenario we need like to resolve public storage endpoints in the internal network and with azure dns custom dns server

[@josevelasco3245]

If you have multiple DNS servers on-prem, can you simply add more destination IPs @ 6:23 or do you create another rule for each on-prem DNS server?

[@krishnakanthbommaraju-gb6el]

I have done everything shown in the video when I do nslookup for onprem dns it goes to azure wireserver ip and shows timedout error. However ping works fine

[@complexxl9]

do you have a video on using private dns resolver for split horizon config? I want to forward requests for dns records that are not available in my private dns zone to some public DNS server like 8.8.8.8, so far unsuccessfully.

[@alozborne]

In a use case where there are Active Directory DCs both on prem and in Azure (self managed, AD DCs running in a VM), is there a reason to favour private DNS resolvers over using custom DNS in Azure and having VMs running in Azure resolve DNS via Windows DNS running on the DCs?

[@svensivic]

I've done everything as in video, but the issue persists. Can a DNS private resolver be used to extend the on premise domain to Azure? So that the servers in Azure can be domain joined with on prem domain? Thnaks

[@Ciraltos]

It won’t extend on-prem DNS to Azure, but it can forward requests for on-Orem domains to win DNS servers. If the goal is to join Azure computers to Win AD, you could add DCs to Azure and set custom DNS on the VNet to use them.

[@svensivic]

@@Ciraltos thank you for clarification. My ultimate goal is to extend on-prem domain so that I can have windows servers in the same domain as on premise. But thinking about it now, maybe I should put one DC in azure and create new domain (same name just put azure in front) and just put conditional forwarders between on prem and azure dns servers.

[@mrsaikrissh]

I used this solution to resolve Azure's private DNS from on-premises. This solves one problem while creating another. If a private is not connected to a vnet (In which Private DNS resolver deployed and linked to itself). It only resolves private DNS entries that are linked to it, and the request is dropped if the entry is not in the private DNS zone linked to the vNet. It should try to public endpoint but that fails. It is not the better suite for this scenario.

[@DMCnME]

Exactly this. With PR you can resolve private zones in your AAD instance. But it breaks your ability to resolve public zones (of the same name) in another company's AAD instance.

[@rinku-blogadmin]

great