{"id":1107,"date":"2018-02-22T13:00:44","date_gmt":"2018-02-22T13:00:44","guid":{"rendered":"https:\/\/www.my-proxy.com\/blog\/?p=1107"},"modified":"2024-05-26T00:45:47","modified_gmt":"2024-05-26T00:45:47","slug":"dns-leak-ip","status":"publish","type":"post","link":"https:\/\/free-proxy-list.net\/blog\/dns-leak-ip","title":{"rendered":"Does DNS Test Leak My Real IP Address?"},"content":{"rendered":"\n

Question: I use a UK IP address in My IP Hide<\/a>. But the DNS leak test shows my DNS servers are in Belgium. Does it leak my real IP address?<\/p>\n\n\n\n

Answer: The short answer is No<\/strong>. Below is a detailed explanation.<\/p>\n\n\n\n

Websites Know Your DNS IP?<\/h2>\n\n\n\n

The websites which can show our DNS servers are using the same technology. We use this one as an example: https:\/\/dnsleaktest.com<\/a><\/p>\n\n\n\n

Here is the test result for our My IP Hide server 213.229.74.238 (UK5).<\/p>\n\n\n\n

\"DNS
DNS Leak Test for UK5 Proxy<\/figcaption><\/figure>\n\n\n\n

It seems that the website dnsleaktest.com knows our DNS servers. In fact, it only knows the ISP of our DNS because our real DNS servers are 8.8.8.8 and 8.8.4.4 instead of 74.125.x.x.<\/p>\n\n\n\n\n\n\n\n

Let’s see how it detects our DNS servers. First, it makes six new domain names such as these ones.<\/p>\n\n\n\n

mx8wdhdrls.dnsleaktest.com\nsxg1h57t5o.dnsleaktest.com\nnnm7ra7ubq.dnsleaktest.com\no69mq7i0a2.dnsleaktest.com\nd4hciffhoy.dnsleaktest.com\n988rgz5xdg.dnsleaktest.com<\/pre>\n\n\n\n
Then it uses javascript to make our browser to connect to those domain names. Our browser needs to know the IP address of them. So it makes a DNS query: “What is the IP address of mx8wdhdrls.dnsleaktest.com”.<\/p>\n\n\n\n
The query route looks like this: Our Browser -> UK5 Proxy<\/strong> -> 8.8.8.8 -> other Google DNS servers ->  74.125.x.x<\/strong> -> the name server of dnsleaktest.com (ns1.dnsleaktest.com)<\/p>\n\n\n\n
What Are Those DNS IP?<\/h2>\n\n\n\n
Then the name server of dnsleaktest.com knows we used 74.125.x.x<\/strong> to do a DNS query. It made six new domain names so it can get six  IP addresses that query those six new domain names.<\/p>\n\n\n\n
But those IP addresses 74.125.x.x are just edge DNS servers that are on the optimal route. ns1.dnsleaktest.com can’t even know their previous nodes. Neither can it know our real DNS servers (8.8.8.8) or our real IP address<\/strong> which is behind the UK5 proxy. What it actually knows is our DNS provider, Google.<\/p>\n\n\n\n
Use DNS Test to Check User’s IP?<\/h2>\n\n\n\n
First, the DNS test can’t get the user’s exact location. For example, websites may get Belgium IP addresses for all the European users, and Taiwan IP addresses for all the Asian users if the users are using Google DNS 8.8.8.8.<\/p>\n\n\n\n
Second, the DNS test is costly. It needs extra code to make many one-off domain names and read the logs from the name servers. It also wastes the Internet resources, by adding unnecessary DNS queries for those disposable domain names.<\/p>\n\n\n\n
Because of the above two reasons (no exact location and costly), most websites won’t use the DNS test to block foreign visitors. Getting the IP address from the user’s HTTP request<\/a> is still the main method.<\/p>\n\n\n\n
The Meaning of DNS Leak Test<\/h2>\n\n\n\n
If you don’t use any proxy\/VPN and use the default DNS server settings. You should be using the DNS server of your ISP. You will see Comcast, Verizon, or AT&T<\/strong> in the DNS Leak test result.<\/p>\n\n\n\n
In that case, your ISP knows all your DNS queries. Thus it can know all the websites you visited.  That is a DNS leak.<\/strong> Some bad ISP may send fake or invalid IP addresses to your DNS queries. Thus it can block some websites.<\/p>\n\n\n\n
Moreover, a DNS test may know your exact location if you are using the default DNS servers of your ISP.<\/p>\n\n\n\n
The meaning of the DNS leak test is to check whether you are using a safe DNS provider.<\/strong> These are safe DNS providers.<\/p>\n\n\n\n
DNS Provider Name<\/th>Primary Address<\/th>Secondary Address<\/th>Feature<\/th><\/tr><\/thead>
Google<\/a><\/td>8.8.8.8<\/td>8.8.4.4<\/td>unfiltered<\/td><\/tr>
Cloudflare<\/a><\/td>1.1.1.1<\/td>1.0.0.1<\/td>unfiltered<\/td><\/tr>
OpenDNS Home<\/a><\/td>208.67.222.222<\/td>208.67.220.220<\/td>secure<\/td><\/tr>
Level3<\/a><\/td>209.244.0.3<\/td>209.244.0.4<\/td>unfiltered<\/td><\/tr>
Verisign<\/a><\/td>64.6.64.6<\/td>64.6.65.6<\/td>unfiltered<\/td><\/tr>
DNS.WATCH<\/a><\/td>84.200.69.80<\/td>84.200.70.40<\/td>unfiltered<\/td><\/tr>
Comodo Secure DNS<\/a><\/td>8.26.56.26<\/td>8.20.247.20<\/td>secure<\/td><\/tr>
Norton ConnectSafe<\/a><\/td>199.85.126.10<\/td>199.85.127.10<\/td>secure<\/td><\/tr>
Quad9<\/a><\/td>9.9.9.9<\/td>149.112.112.112<\/td>secure<\/td><\/tr>
SafeDNS<\/a><\/td>195.46.39.39<\/td>195.46.39.40<\/td>secure<\/td><\/tr>
CleanBrowsing<\/a><\/td>185.228.168.9<\/td>185.228.168.10<\/td>filtered<\/td><\/tr>
FreeDNS<\/a><\/td>45.33.97.5<\/td>172.104.237.57<\/td>unfiltered<\/td><\/tr>
Alternate DNS<\/a><\/td>76.76.19.19<\/td><\/td>ad-free<\/td><\/tr>
Yandex.DNS<\/a><\/td>77.88.8.8<\/td>77.88.8.1<\/td>unfiltered<\/td><\/tr>
UncensoredDNS<\/a><\/td>91.239.100.100<\/td>89.233.43.71<\/td><\/td><\/tr>
Hurricane Electric<\/a><\/td>74.82.42.42<\/td> <\/td><\/td><\/tr>
puntCAT<\/a><\/td>109.69.8.51<\/td> <\/td><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
How to Fix a DNS Leak<\/h2>\n\n\n\n