Quantcast
Channel: Azure Networking (DNS, Traffic Manager, VPN, VNET) forum
Viewing all articles
Browse latest Browse all 6513

Hybrid VNET DNS servers forwarding requests to public DNS servers

$
0
0

I have set up a classic hybrid network between my on prem network and Azure network. The azure net has AD and file servers and the cloud services in which they reside are configured with my on prem DNS servers and all servers work fine.
My on prem DNS servers are forwarding DNS requests properly for zones/hosts that they do not own, like google.com, cnn.com, etc... but they are also trying to resolve a number of hostnames that include stuff like:

***************

wpad.cs-aaaa.j9.internal.cloudapp.net

wpad.cs-bbbb.j6.internal.cloudapp.net

wpad.cs-cccc.j10.internal.cloudapp.net

*.l.google.com

outlook.office365.com

sl1.sal.avaya.com

isatap.cs-aaaa.j9.internal.cloudapp.net

isatap.cs-cccc.j10.internal.cloudapp.net

teredo.ipv6.microsoft.com.nsatc.net

***************

where aaaa, bbbb, cccc are my cloud service names.

These requests are being sent to my external DNS resolvers, but I don't understand why or which server or part of Azure is making this request. It seems like those are Azure internal names that should be resolved internally and not by my on prem DNS or their external forwarders, neither of which can resolve the requests.

Can anybody help me understand why this is occurring or how to rectify it?

Thanks,
Brit


Viewing all articles
Browse latest Browse all 6513

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>