Private Endpoints in Azure provide a secure way to access resources over the private, internal network. But the options for configuring DNS for Private Endpoints is not as straight forward. This video goes over the options available for DNS with Private Endpoints. We start by crating a storage account with a Private Endpoint, the review the default DNS configuration. We look at The WireServer and how it can be used with a Conditional Forwarder as well as using Forward Lookup Zones for name resolution.
Links:
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
Two Azure IP Addresses You Should Know
https://youtu.be/EwLJI2qy-80
2 thoughts on “Private Endpoints and DNS in Azure”
Hi Travis,
awesome video!
I’ve configured Forward Lookup Zone in my DNS on Windows Azure VM for my privatelink dns records for database, redis cache and storage in my VNET and other peereds VNETs.
There is only a little problem: I’ve to contact a blob storage of another supplier that gave me the public FQDN to connect to his public storage demo_supplier.blob.core.windows.net.
The problem is that also him have privatelink configured on his Azure account, but I want only his public IP and my DNS Server search on privatelink forward lookup zone created.
There is a workaround?
Thank you very much
Davide
Pingback: I know how Private Endpoints and DNS in Azure - Center of hosting solution