question

TrentQ avatar image
0 Votes"
TrentQ asked TrentQ commented

Custom DNS entries in the xml configuration file don't work for P2S VPN client

Hi

I added to the config xml

<dnsservers>
<dnsserver>172.16.1.7</dnsserver>
</dnsservers>

When connected the client logs shows:

(configureDNSSettings(clientConfig:settings:profileName:)) No DNS configuration specified.

and I can't resolve any on-prem resources by FQDN, only by IP.

azure-vpn-gateway
· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@TrentQueen-9536 Was the custom DNS server added after establishing the P2S connection? The reasoning for this question is that after making any network change, whether it is in Azure side or on-prem side, on a P2S connection, the VPN client must be downloaded again and reinstalled in order for the changes to take effect. Otherwise, issues such as this one are likely to occur. Please let me know. Thank you!

0 Votes 0 ·

@TrentQueen-9536 Any update?

0 Votes 0 ·

It seems that if you don't have a custom DNS server set in the vNet the downloaded client config XML is malformed.

0 Votes 0 ·

1 Answer

Dev073 avatar image
0 Votes"
Dev073 answered

Hope the updated DNS config.xml is imported properly to machine after the changes in entries.

Discussed about resolution here :

https://docs.microsoft.com/en-us/answers/questions/64223/issue-with-resolving-hostnames-while-connected-to.html

Point-to-site VPN client normally uses Azure DNS servers that are configured in the Azure virtual network. 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. If the Azure DNS servers do not have the records for the local resources, the query fails.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. To do this, you can use DNS Forwarders or Conditional forwarders.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.