Point-to-Site VPN DNS issue
After connecting the VPN client on windows 10 machine, I faced two differences in communication:
When I connected through WiFi, I am able to communicate Azure VNET.
But When I connected through Ethernet cable, I am unable to communicate to Azure VNET.
This is because of traffic route, which change according to Metric value of the Network Adapter. So by changing this metric value to 100 for ipv4 and ipv6, I am able to communicate to Azure VNET from Ethernet connection.
But, it's not the reliable way to change it for each machine Ethernet adapter. So, "I am expecting the least value and high priority of the Metric for the VPN client software in itself".
Used commands to change the metric:
netsh interface ipv4 set interface Ethernet metric=100
netsh interface ipv6 set interface Ethernet metric=100
Similar issue on the page no. 4 of below article: