"One caveat to that is that modern browsers may be (i think it's on by default 
with firefox) doing their own DNS via DNS-over-HTTPS or
DNS-over-TLS, so stand alone tools like dig or nslookup might give
different results than your browser."

Possibly, my networking-fu ain't what it used to be and much has changed in the 
meantime.

However, what you're really trying to is compare what an Internet DNS, like 
Google's 8.8.8.8 or 8.8.4.4 resolves wunderground.com to and what you the pc's 
local dns cache and/or the ISP's DNS resolves it to.

For many years, whenever possible, I always reconfigure my DNS to point to 
Google's or OSU's public DNS, both ipv4 and ipv6.

Lately, I've had really good results running SmartDNS instead of some other 
local DNS caching like djbdns. 

Nothing bugs me more than waiting for a web site to load while I see all this 
back & forth communication in the left hand corner of my browser. Especially 
when I see redirects to F!facebook,twitter, and whatever other BS non-sense 
that I don't use.

Reply via email to