Powershell Get -DnsClientNrptPolicy showed the correct local dns server was assignedĤ. Azure VPN client showed the DNS server when connected and IpConfig did NOT show the dns serverģ. The virtual network in Azure is assigned a local VM DNS server (internal IP)Ģ. I had this issue and spent 3 days trying to find an answer.ġ. Please don’t forget to " Accept the answer" wherever the information provided helps you, this can be beneficial to other community members. Kindly let us know if you need any further assistance on this issue from our end. You can refer the below article for this issue: For more information, see Name resolution using your own DNS server To do this, you can use DNS Forwarders or Conditional forwarders. To resolve the problem, make sure that the Azure DNS servers that used on the Azure virtual network can resolve the DNS records for local resources. If the Azure DNS servers do not have the records for the local resources, the query fails. The Azure DNS servers take precedence over the local DNS servers that are configured in the client (unless the metric of the Ethernet interface is lower), so all DNS queries are sent to the Azure DNS servers. Point-to-site VPN client normally uses Azure DNS servers that are configured in the Azure virtual network. When the client connects to Azure by using point-to-site VPN connection, it cannot resolve the FQDN of the resources in your local domain.
This is a known issue and is documented as below:
0 kommentar(er)
