I'm trying to set up a hybrid connection from my on-premises network to Azure. I've implemented Azure DNS private resolver, private DNS zones, and private endpoints. My goal is to determine if I can use a custom DNS in my spoke network and whether the same inbound endpoint IP can also serve as a custom DNS in the hub VNet to avoid using Azure's default DNS. My client prefers not to use the default DNS zone values. For example, instead of the typical blob storage endpoint value, they want to use a custom value like myorg.blob.xyz.com to resolve the private endpoint from the on-premise network. Is this possible?
2 Answers
Generally, yeah, you'll need to peer your networks and link the DNS resolver along with your private link zones. One DNS resolver IP in the hub can work and connect to multiple spokes. If you're setting custom DNS zones for each service, that should tackle your situation. This way, your custom DNS entries will be respected across your virtual networks.
It sounds like you're trying to sidestep Azure's default DNS settings. You can definitely set up custom DNS in your spoke networks, and as for your hub VNet, using the resolver's IP as a custom DNS is a valid approach. Just ensure you configure the resolver correctly along with the private link zones. This way, you can have flexibility with the DNS entries based on your client’s preferences.
Related Questions
Cloudflare Origin SSL Certificate Setup Guide
How To Effectively Monetize A Site With Ads