Weird result in https://ipleak.net w Simple DNSCrypt + 1.1.1.1


#1

Simple DNSCrypt updated itself to version 0.5.5 (64-bit), and it shows it is now using dnscrypt-proxy 2.0.14, so that’s good.

It continues to run well. In Simple DNSCrypt, I have again selected cloudflare’s 1.1.1.1 as my ONLY resolver, and it shows exclusively when I go to https://www.dnsleaktest.com/ .

HOWEVER, if I go to a deeper test at https://ipleak.net/ , I get one odd result: In the DNS Address section, the result is “0 servers, 100 errors”. Why?

By the way, my nslookups are running well. Here’s a sample:

arstechnica
Server: localhost
Address: ::1
Name: arstechnica.com
Address: 50.31.169.131
cloudflare
Server: localhost
Address: ::1
Name: cloudflare.com
Addresses: 198.41.215.162
198.41.214.162

Also, my PC is Win 7 Pro 64-bit, and my ISP is Verizon FIOS 1Gbps, which does NOT support IPv6.

Thanks.


#2

Well. I guess this should say enough about this beatyful service:

At the first try there was: 1 DNS (congrats, I’ve two configured) and 7 Errors showing the public IP of my DSL connection. yay. I use OpenDNS since i need to be able to block requests (youth protection). I only trust those services as far as i can throw their servers. And they can be really heavy and unwieldy.


#3

Raspberry PI FTW :crazy_face:


#4

Well… :stuck_out_tongue:

image


#5

Well, if it goes by the throw-ratio you should really trust that machine :wink:


#6

Mark Meyer – you wrote:

MarkMeyer
Well. I guess this should say enough about this beatyful service:

But I don’t think you have a problem with your IP address. If you read carefully, you’ll see that your public IP is NOT in the “Your IP addresses - WebRTC detection” area. Only your internal LAN IP is shown, just as mine is. I think that’s a good result - neither you nor I have WebRTC leaks.

It remains interesting that your “DNS Address” area also shows “0 servers, 100 errors”. Does anyone have a clue why this is happening?


#7

I was not talking about the LAN address. :wink:

It was part of the screenshot because I made it too big and I was too lazy to make a new one. :joy:

It’s about the DNS test where the public IP of my DSL was shown before. It stays as in my last screenshot. 0 and 100 errors.

Different network:


#8

Speculation: Although the DNS queries apparently succeed, perhaps ipleak.net doesn’t detect that they succeeded when random capitalization is used?

This hypothesis could be tested using another DNS server that randomizes case. I don’t really want to give it a shot though. :sweat:


#9

Forgot to mention: in my last post I was using a private DNS with Cloudflare as upstream instead of OpenDNS. Not sure if it destroys your hypothesis ^^