In summary,
I think you'd agree with me that Azure‑provided DNS via the
168.63.129.16 Virtual IP does a lot of work for us.
You find that's a general pattern with Azure virtual networks that that wire
server not only is responsible for Azure‑provided DNS,
it's also responsible for Azure‑provided DHCP,
as well as it serving as your default gateway out of that VNet.
So, a lot of heavy lifting,
but we can override that wire server and take control over
DNS to any extent we're comfortable.
To that point,
you want to think very carefully about your name resolution
strategy in a hybrid cloud infrastructure,
how you want to integrate Azure‑provided DNS,
how you're working with forwarding and conditional forwarding,
and so on and so forth.
Lastly, although it's not formally on the exam,
that Private Link service is rapidly becoming a standard in
terms of providing you a back channel, as it were,
to various Azure services, particularly Azure data services.
So keep that in your mind, and feel free to look in the Pluralsight library and,
of course, the Microsoft Docs for more learning about the Private Link service.
With that,
I want to thank you very much, and I look forward to seeing
you in the next module called Manage IP Addressing in
On‑Premises and Hybrid Scenarios. Thanks very much.