Couple of answers to common questions. 1, To forward ALL requests from Azure DNS to custom DNS where there is no matching private DNS zone linked add a default rule, i.e. domain "." (no quotes) 2, The only private DNS zones resolved are those linked to the vnet where the DNS resolver is deployed
Hey everyone, welcome to another video! Please make sure to read the description for the chapters and key information about this video and others. ⚠ P L E A S E N O T E ⚠ 🔎 If you are looking for content on a particular topic search the channel. If I have something it will be there! 🕰 I don't discuss future content nor take requests for future content so please don't ask 😇 Thanks for watching! 🤙
You jus rock, i can't explain how simple you made it to look like. It would have taken hell lot of time to read through the docs. Explanation is next level, keep doing it. Kudos.
You eliminated so much confusion with this perfect explanation and examples. I'm faced with a similar challenge in our company's hybrid environment and now I have a solid approach. Thanks for sharing your wealth of knowledge and clear perspective! You're amazing!!
This is exactly what I was waiting for. Currently have to you the ugly forwarder route with Azure based DCs and conditional forwarders. A bit of a pain to administer
BRILLIANT thanks John. I really like this service. Definitely the inbound option is something that is going to be useful for us. Once again many thanks John. Great video.
Fantastic! Thank you sir for yet another concise well thought out and explained video on a topic I think everyone using Azure private networking has to have been excitedly waiting for. I know we're happy to be able to kill off some IaaS over here!!
cheers for this John. Not sure on the design decision not to have the same IP for both in and outbound. The resolver is bound to one vnet after all. Inbound is pretty clear but need to play with outbound and multi vnet scenario a bit to understand the ruleset link
Great vid and thank you very much for explaining so neatly, as usual. At the finish it was clear this is like two separate features - "DNS resolver" inbound IP for accessing Azure DNS over private IP, and "DNS forwarder" outbound IP for binding Azure DNS to DNS forwarding rule set. ** Any idea why In and out IPs must be in separate subnets? Seems a bit arbitrary. (And love the t-shirt - congrats on Texas and St George 2 weeks apart, not done one yet and very inspiring to read your blog)
Hey John. Do you have a way for us to tip? This video saved me a ton of time and will allow me to resolve an issue very quickly today. Would love to send you a few bucks in return. Just not sure how. Great job as usual and thank you!
That is very kind but not required. This site is my way of giving back and helping. I don't want to make any money from it which is why all advertising is turned off. Appreciate the gesture, we're all good.
After reading docs and trying to wrap my head around exactly what it is this technology is going to do, how it's going to do it and the implications of using it I wasn't able to feel confident in my understanding to implement. I watch another of John Savill's incredible videos and I'm ready to move straight into implementation. YOU ARE A GOD SEND.
Couple of answers to common questions.
1, To forward ALL requests from Azure DNS to custom DNS where there is no matching private DNS zone linked add a default rule, i.e. domain "." (no quotes)
2, The only private DNS zones resolved are those linked to the vnet where the DNS resolver is deployed
Hey everyone, welcome to another video! Please make sure to read the description for the chapters and key information about this video and others.
⚠ P L E A S E N O T E ⚠
🔎 If you are looking for content on a particular topic search the channel. If I have something it will be there!
🕰 I don't discuss future content nor take requests for future content so please don't ask 😇
Thanks for watching!
🤙
This new feature just made my evening, can't wait to remove all the dnsforwarder containers we had to deploy for vpn private link resolving
As always, you make complex things simple and understandable. It requires deep knowledge and art of teaching. Thanks a lot, John.
Hot topic of the year 🔥
I don't think anybody else can explain this concept in a better way. Hats off!!!
Nice! thanks, John. I don't think I would have ever understood this from the documentation.
Glad could help
awesome
much needed in todays medium IT industries, who are going to Azure Cloud
thanks for bringing up this topic
It's about time! LOL Great info and very much looking forward to GA for this PaaS offering. Its very much needed.
You jus rock, i can't explain how simple you made it to look like. It would have taken hell lot of time to read through the docs. Explanation is next level, keep doing it. Kudos.
John I think your haunting my mind every time I open TH-cam you pop up with a video about something I was thinking about that day.
ROFL well this is a pretty old video so i think the web was checking on you :D
My Azure DNS knowledge has been lacking and your DNS videos have been amazing. Thank you so much for everything you do!
You’re amazing! Nobody teaches this as straightforward as you do.
Great explanation with a nice simplifying the concept. As a MCT I always refer to your great videos and free! .Much appreciated John!
You eliminated so much confusion with this perfect explanation and examples. I'm faced with a similar challenge in our company's hybrid environment and now I have a solid approach. Thanks for sharing your wealth of knowledge and clear perspective! You're amazing!!
Thank you, we are using this at my job and this clears up how it all works.
Glad it was helpful!
You are really the best while explaining any Azure solution. Thanks a lot !!
This is exactly what I was waiting for. Currently have to you the ugly forwarder route with Azure based DCs and conditional forwarders. A bit of a pain to administer
Really great walkthrough John, solves a lot of issues, and takes away a lot of the current complexity
Thank you! Something trying to clean up right now (old method vs new). As always, fantastic information and flow. Much appreciated!
Awesome! Thanks John, another brilliant deep dive!
BRILLIANT thanks John. I really like this service. Definitely the inbound option is something that is going to be useful for us. Once again many thanks John. Great video.
Very welcome
Another amazing video. Thank you very much John!
Thanks John, great videos as always, found this super helpful and clear when looking to use Azure Private DNS Resolver
Glad it was helpful!
Thanks John, you're an absolute LEGEND
Excellent presentation and contact of topic ! No one can beat you !
Outstanding depiction , a quite complex topic broken down into easy-to-digest pieces!
Finally, I understood! Thank you for making it so easy :)
Glad it helped!
Your videos are just awesome and clear! Thanks!
Glad you like them!
Fantastic! Thank you sir for yet another concise well thought out and explained video on a topic I think everyone using Azure private networking has to have been excitedly waiting for. I know we're happy to be able to kill off some IaaS over here!!
@John Savil - As usual fantastic presentation. Thanks a lot. 🙂
Awesome walk through as always! You present things so clearly.
Thanks so much!
Thanks John! Really great tutorial for understanding the concept.
Great explanation. Only problem is I'm supposed to be sleeping. Now I'm itching to get this setup and see it work!
Awesome!! Azure is great and your channel too!
That's absolutely fantastic. Thanks a lot.
Thank you very much, subscribed. You helped with an issue i was having problems understanding.
Awesome thank you John sir you Rock
Hehe thanks 🤙
Amazing tutorial as always. Thank you.
Really great video, thank you
I was just stuck with that same issue for Azure Function and I think this might just solve it. Will give it a try ASAP
superb and easy to understand
Brilliant 😊
cheers for this John. Not sure on the design decision not to have the same IP for both in and outbound. The resolver is bound to one vnet after all. Inbound is pretty clear but need to play with outbound and multi vnet scenario a bit to understand the ruleset link
Think about scalability and not wanting to share endpoint for inbound requests and going outbound for resolutions.
Too good, overridden MS docs, Thanks
|Interesting. Thanks John
That's cool! I hope this service is for free now. Thank you.
It will be a paid service at release I’m sure
This went GA this week, so i can finally get it installed and remove our homemade interim solution.
Great vid and thank you very much for explaining so neatly, as usual. At the finish it was clear this is like two separate features - "DNS resolver" inbound IP for accessing Azure DNS over private IP, and "DNS forwarder" outbound IP for binding Azure DNS to DNS forwarding rule set. ** Any idea why In and out IPs must be in separate subnets? Seems a bit arbitrary.
(And love the t-shirt - congrats on Texas and St George 2 weeks apart, not done one yet and very inspiring to read your blog)
And your Uber driver was Patrick Curtis - great encounter! Hiliarious
Separation for scale purposes likely more important post GA. Thanks re the events :)
Great!
Thanks
I wonder how the pricing will compare to running one or more DNS resolver VMs.
Sure pricing will be published ahead or at GA
Hey John. Do you have a way for us to tip? This video saved me a ton of time and will allow me to resolve an issue very quickly today. Would love to send you a few bucks in return. Just not sure how. Great job as usual and thank you!
That is very kind but not required. This site is my way of giving back and helping. I don't want to make any money from it which is why all advertising is turned off. Appreciate the gesture, we're all good.
Nice 👍
Is this in gov.?
Don't believe so yet.
After reading docs and trying to wrap my head around exactly what it is this technology is going to do, how it's going to do it and the implications of using it I wasn't able to feel confident in my understanding to implement. I watch another of John Savill's incredible videos and I'm ready to move straight into implementation. YOU ARE A GOD SEND.
Love your videos but this one was a bit hard to follow.