Score:0

How do I get onsite DNS to communicate with Azure VNet DNS?

ne flag

We have an S2S and our DNS server in Azure can talk with the Azure VNET DNS, however our onsite DNS server cannot because of a routing issue I think.

What configuration do I need to change so that requests from our local DNS server forwarding to 168.63.129.16 go through our S2S connection to the Azure VNET? I already have the conditional forwarder added for core.windows.net.

We have a Meraki if you need to know that.

naps1saps avatar
ne flag
Instead of adding `168.63.129.16` to the conditional forwarder on the local DNS, I added the local IP of the DNS server in Azure which then conditional forwards to `168.63.129.16`. That seems to be working but is a single point of failure. I'd like to be able to do it the right way.
br flag
Azure Private DNS Resolver is now in preview which will let you do what you want
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.