How to Use Azure DNS Private Resolver and Outbound Endpoints
This video goes over how to use an Azure DNS Private Resolver and Outbound Endpoints with Azure DNS Forwarding Rulesets. These two services allow us to resolve on-premises host names from Azure clients. We no longer need to deploy DNS servers in Azure to bridge on-premises and Windows DNS with Azure DNS. We can leverage the Azure DNS Private Resolver PaaS service to handle DNS lookups for Azure.
00:00 – Start
03:38 – Test Without Outbound Endpoint
04:19 – Add an Outbound Endpoint
05:18 – Create a Forwarding Ruleset
08:55 – Test with Outbound Endpoint
Free Azure guide! Subscribe to the newsletter
https://subscribepage.io/rbsIjt
Zero to Hero with Azure Virtual Desktop
https://www.udemy.com/course/zero-to-hero-with-windows-virtual-desktop/?referralCode=B2FE49E6FCEE7A7EA8D4
Hybrid Identity with Windows AD and Azure AD
https://www.udemy.com/course/hybrid-identity-and-azure-active-directory/?referralCode=7F62C4C6FD05C73ACCC3
Windows 365 Enterprise and Intune Management
https://www.udemy.com/course/windows-365-enterprise-and-intune-management/?referralCode=4A1ED105341D0AA20D2E
Cost Management in Azure
https://www.udemy.com/course/cost-management-in-azure/?referralCode=49438F3AF971E9CB0439
by Travis Roberts
linux dns server
great
on-prem domain and private zone domain are same. Outbound resolver will resolve or VM's will to private zone
thanks for your content
What if scenario we need like to resolve public storage endpoints in the internal network and with azure dns custom dns server
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.
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
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?
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
Thanks for this excellent content Travis