I kept running into DNS issues, and needed to triple-check that I was pointing to the right DNS servers, so I made this utility website that does exactly that: which-dns [1]<p>This isn't a new idea ([2]), but mine supports https (hat tip to Matt Holt's certmagic [3]), is ad-free, and the source is available [4].<p>Let me know what you think!<p>[1] <a href="https://which.nameserve.rs" rel="nofollow">https://which.nameserve.rs</a><p>[2] <a href="http://www.whatsmydnsserver.com/" rel="nofollow">http://www.whatsmydnsserver.com/</a><p>[3] <a href="https://github.com/caddyserver/certmagic" rel="nofollow">https://github.com/caddyserver/certmagic</a><p>[4] AGPL. It is my first foray into golang. <a href="https://github.com/redirect2me/which-dns" rel="nofollow">https://github.com/redirect2me/which-dns</a>
Doesn't show IPv6 for me.<p>I always use IPleak.net [1]. Works for public IPv4, IPv6, DNS server, Tor/AirVPN exit node, BitTorrent, geolocation, and all kind of browser metadata.<p>Browsing through comments shows this can do some things IPleak.net can't do such using wget/curl with API.<p>[1] <a href="https://ipleak.net" rel="nofollow">https://ipleak.net</a>
You can check your best available dns server via this easy tool <a href="https://www.grc.com/dns/benchmark.htm" rel="nofollow">https://www.grc.com/dns/benchmark.htm</a> (win and wine)
This is really cool, especially because I can just 'wget -qO- $RANDOM.which.nameserve.rs/api.json?callback=myfunction' which means I can use this in scripts. (For example an added field to scripts that grab from ifconfig.co)
I have a local DNS server that forwards over TLS (DoT) to Cloudflare & Quad9, round-robin.<p>Page alternately returns WOODYNET @ rrdns.pch.net and CLOUDFLARENET. I like the pch.net info - it's something about Quad9 I didn't know.
I run my own DNS servers at home. I have a small virtualization cluster and run a small DNS vm on each physical host.<p>My resolvers perform queries against the root servers directly and cache results.<p>It's refreshing to skip all the DNS fuckery that's going on nowadays.
If Mozilla silently enabled DOH-via-CloudFlare for you, it would show up here right? Because if yes, this would make it quite easy to find whether you have the right settings without having to find it somewhere in a configuration screen or trying to find out which users' throats Mozilla ended up deciding to force this down.
Neat, this helped me realize I haven't switched away from my provider's default DNS when I moved in, which is something I usually do.<p>How to choose a DNS server? I usually just go with 8.8.8.8/8.8.4.4, I used to always test this with Namebench (<a href="https://en.wikipedia.org/wiki/Namebench" rel="nofollow">https://en.wikipedia.org/wiki/Namebench</a>) and these always turned out as the fastest - but it looks like it hasn't been updated since 2010 - are there any better tools for this, or any considerations in general? I prefer performance over privacy here, I think privacy should be on a different layer.
It would be neat if this also recognized that you're hosting your own dns, instead of spitting your own IP back at you. I didn't recognize my IP at first.
Unrelated, but I found a typo on this page:<p><a href="https://resolve.rs/http/myheaders.html" rel="nofollow">https://resolve.rs/http/myheaders.html</a><p>It says:<p>> These are the HTTP headers that are being sent my your browser.<p>Great set of tools, BTW.
DIY script to find out the fastest DNS for you;<p>for i in `cat dns_list.txt|grep -v '^#'`
do
qt=`dig @$i archive.is| grep "Query time:" |cut -f2 -d ':'`
echo "$i: $qt"
done
I've added an "Alternatives" section [1] to the README with several of the sites/services/etc mentioned in this HN thread.<p>[1] <a href="https://github.com/redirect2me/which-dns#alternatives" rel="nofollow">https://github.com/redirect2me/which-dns#alternatives</a>
> I specifically made the API be JSONP only (i.e. you need to provide a callback parameter), so if you abuse it, bad things will happen to your clients!<p>Is OP threatening to inject harmful code into abusers' script tags, or am I totally misreading this.
This shows which DNS server performed the recursive query for you, but in more complicated setups it won't be the DNS server your system is pointed to. For example if you're using 1.1.1.1, this will show some other CloudFlare IP.
Did one for my project that discovers more servers [1]
Not an easy task I tell you that.<p>[1] <a href="https://dnsadblock.com/dns-leak-test/" rel="nofollow">https://dnsadblock.com/dns-leak-test/</a>