Windows 10: Vpn leak !!!warning!!!

Windows 10 uses a method of resolving DNS requests that completely ignores the fact that you are connected to a VPN and exposes you true IP address to every web site you visit.

If you are using VPN and think you are anonymous try these sites and find out if you really are.
DNS leak test
Web-based DNS Randomness Test | DNS-OARC
IP/DNS Detect

The only method that I found that actually worked using open VPN was the fix-dns-leak-32.dll or fix-dns-leak-64-dll
https://help.tigervpn.com/support/so...penvpn-win-10-

FOR PPTP do this :

gpedit.msc
Computer Configuration\Administrative Templates\Network\DNS Client\ and enable the key
DisableSmartNameResolution

and for PPTP AND OPENVPN:

1. Go to Start
2. Click Settings
3. Click Network and Internet
4. Click Change Adapter Options
5. Choose your normal internet connection (Ethernet/Wifi). DO NOT make these changes to the TAP connection
6. Right click and press Properties
7. Under the Networking tab, select the TCP/IP v4 and then click Properties
8. Change "Obtain DNS server address automatically" to "Use the following DNS server address"
9. Enter 209.222.18.222 for the Preferred DNS server
10. Enter 209.222.18.218 for the Alternate DNS server
11. Press OK

:)

 

my location

DNS Leak maybe?

How DNS Leaks Can Destroy Anonymity When Using a VPN, And How to Stop Them



Change your DNS settings to use Google's. hah

(8.8.8.8 and 8.8.4.4)

 

Win 10: DNS resolution of remote network via VPN connection not working

I spun up a fresh install of Windows 10 in a VM to test on after seeing this issue on every physical Win10 machine I have. I tested all of the answers in this thread and none of them worked. I discovered that the solution is to combine the answers posted
by "Keenans" and "ECC-Dan".

Control Panel > Network and Sharing Center > Change adapter settings > Right click your Ethernet or Wifi adapter > Properties > double click IPv4 > Advanced > Uncheck Automatic Metric > Enter 15 for interface metric > OK > OK.

On that same Properties page, double click IPv6 > Advanced > Uncheck Automatic Metric > Enter 15 for interface metric > OK > OK.

Only after changing both of those settings is the issue resolved. I tested changing either one back and it breaks again. After changing both I ran nslookup from command line and it returned the DNS server on the remote network where the VPN is connected
to, where as otherwise it would return the local DNS server. I then used Wireshark capturing on the Ethernet interface, did some pings to random websites, and verified that there were no DNS packets captured. This proves that after making the changes, DNS
queries are being sent ONLY over the VPN connection, and not simultaneously over all connections (which is known as the Win10 DNS leak). So this is also part of the solution for the Win10 DNS leak:

WARNING! Windows 10 VPN Users at Big Risk of DNS Leak - BestVPN.com

Beware of Windows 10 DNS resolver and DNS Leaks – ValdikSS – Medium

Note that fix the DNS leak, you first need to do the steps above. Then you need to set two registry values. The linked articles only list one, which by itself, does not fix the issue in newer builds of Win10. Set these registry values:

Key: HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows NT\DNSClient

Value: DisableSmartNameResolution

Data: 1

Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dnscache\Parameters

Value: DisableParallelAandAAAA

Data: 1

Only after doing all of that, will your DNS client behavior be back to the way it was in Win7. You have to wonder how this got through QA at Microsoft.