Azure client not resolving DNS

Good Day

we recently created a site to site VPN in azure. we created a server in azure and attempted to add it to our on premise domain. a DNS server was configured in the network connection and the dns server itself seems to meet all prerequisites, i.e ddns on and scavenging off etc. however while i can ping machines locally using IP and cannot do so using dns. also when attempting to add the azure server to the domain i get a dns error. nslookup also shows unknown for the server name.

any guidance will be appreciated

thanks

June 17th, 2015 1:00pm

When creating an Azure vnet, you will need to register/specify your DNS which also needs to be within the address range of a target subnet. Upon the DNS is deployed, set it with an intended and static IP. Normally in this scenario, a DC/DNS is first deployed and set with the target IP. Subsequently additional VMs deploy to this vnet will then look for this DNS for resolving names. HTH. 

Free Windows Admin Tool Kit Click here and download it now
July 9th, 2015 3:55pm

Thank you for your response, but I managed to resolve the issue. it seems that the checkpoint VPN had an implicit rule for DNS which as a result was allowing the DNS traffic to pass in clear text. we managed to resolve the issue by moving this rule lower down in the rule base allowing the Traffic to encrypt and successfully pass through the VPN.

  • Marked as answer by dnlsingh 11 hours 21 minutes ago
July 9th, 2015 3:59pm

Thank you for your response, but I managed to resolve the issue. it seems that the checkpoint VPN had an implicit rule for DNS which as a result was allowing the DNS traffic to pass in clear text. we managed to resolve the issue by moving this rule lower down in the rule base allowing the Traffic to encrypt and successfully pass through the VPN.

  • Marked as answer by dnlsingh Thursday, July 09, 2015 7:58 PM
Free Windows Admin Tool Kit Click here and download it now
July 9th, 2015 7:57pm

Thank you for your response, but I managed to resolve the issue. it seems that the checkpoint VPN had an implicit rule for DNS which as a result was allowing the DNS traffic to pass in clear text. we managed to resolve the issue by moving this rule lower down in the rule base allowing the Traffic to encrypt and successfully pass through the VPN.

  • Marked as answer by dnlsingh Thursday, July 09, 2015 7:58 PM
July 9th, 2015 7:57pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics