Private Endpoints and DNS Part Deux: Azure Private DNS Zones
Вставка
- Опубліковано 19 лют 2022
- This is a second video on Azure Private Endpoints and DNS. Previously, we reviewed options for DNS name resolution with Private Endpoint that included a forward lookup zone for the privatelink.file.windows.core.net zone. That option required manually adding hosts to the DNS zone. In this video, we review a hub-and-spoke configuration leveraging a forwarder server in Azure and conditional forwarding in Windows DNS. Although slightly more complicated, this option does not require manually adding host to the DNS lookup zone.
3:19 Create a Storage Account with PEP
5:49 Review Private DNS Zones
6:29 Add Storage Account DNS Configuration
9:52 Conditional Forwarder
Links:
Zero to Hero with Azure Virtual Desktop
www.udemy.com/course/zero-to-...
Hybrid Identity with Windows AD and Azure AD
www.udemy.com/course/hybrid-i...
Private Endpoints and DNS in Azure
• Private Endpoints and ...
Two Azure IP Addresses You Should Know
• Two Azure IP Addresses... - Наука та технологія
Thank you so much for this great explanation.
I always find your videos super helpful.
thank you for the video. The new managed service "DNS private resolver" does the exact same thing but with additional features
Most enterprise dns has api. You can use powershell to automate the dns during the build process. Cool video though, thanks!
Great video thanks! So, what would you do if you didn't have a private DNS zone in your hub? Would you create them manually and if so, would you need to add something into the Virtual network links on the private DNS zone for your spoke VNETs?
Awesome video! Could you please make another video demonstrating how to leverage Azure DNS Private Resolver with inbound and outbound endpoints to resolve Azure Private Endpoints from On-Prem Windows DNS server, as well as reverse resolving from Azure to on-Premises? Thanks in advance and looking forward to the demo :)
I just did in my last two videos. You can find the first here ua-cam.com/video/XnPaJkV4rBE/v-deo.html
What I can't understand is why you would forward DNS from your DC to another DNS forwarder. Why wouldn't you just attach the private DNS zone to the vNet containing your DCs?
That is fine if all the DC’s are on the same VNet. If the DC’s are on other VNet’s or outside Azure they won’t have access to that private DNS zone and the lookup to those DC’s would fail.
I may have missed it from a previous video, but is vnet peering configured between the 3 vnets ?
Thanks for the video, i tríes to replícate it in my environment, however, on a server that is standalone DNS, i aleyas get the ip from the interface and not from the privatelink.
Is there an easy way to resolve multiple hostnames in a private DNS zone? I have about 900 hostnames and Ip addresses I need to add on my private DNS zone, Should I be adding all of them manually? I checked with a couple of them and it works, the Private DNS zone returns the corresponding IP but how do I do it for a really big IP & hostname range?
Do you have Custom DNS setup on the vNet that the DNS forwarder lives on? Or are you using the Default (Azure Provided) DNS on that vNet?
Great video as usual, i do have a question / clarification if possible, when testing the solution and trying to change the DNS configuration for a specific PEP, i am always receiving the error : A configuration already exists with a private DNS name with the same name !! however i has a able to achieve the same result using the virtual network link withing the DNS private zone to link different VNETs. what do you thing is the problem !!
I had the same issue. I then created a new Sub, VNET & Storage Ac (SA) which performed as shown in Travis's example. I think the difference was setting SA to Public Access disabled (I previously has Selected Networks).
Would the new Azure private DNS resolver resolve the issues with the wireserver being able to only see the private endpoint dns records local to the vnet?
i haven't actual tested but do plan to test.. indeed the new Azure private dns resolver should be able to resolve PEP across vnets. if so i this is a game changer . thrid party DNS Appliances out the door .he-he..
great videos and great explanations. Is there a way to use these when using a Split Tunnel VPN like Azure VPN?
Not sure, the tunnel would need to use internal DNS.
Microsoft recommended having just one private dns zone for each private endpoint type in the hub network. When you create the private endpoint in the spokes and register it to DNS, just select the private endpoint dns zone on the hub instead of creating new private dns zone in the spoke. Isn't that a simpler option that having to merge it manually in the hub from the different spoke private zones?
This is too complicated and not easy to understand still