Re: [PLUG] Weather underground no longer reached by browser
"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.
Re: [PLUG] Weather underground no longer reached by browser
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. -- Russell Senior russ...@personaltelco.net On Thu, Feb 1, 2024 at 2:48 PM MC_Sequoia wrote: > I'm just speculating here, but I'm guessing you might have ran into a > stale DNS entry due to some change upstream, etc. > > Try direct URL again, in guessing your location DNS cache got updated. > > In the future, don't ping URL, use nslookuo or dig command on > wunderground.com. If you can't DNS name resolution to an IP address, then > that's what's going on > > Sent from Proton Mail mobile > > Original Message > On Feb 1, 2024, 2:41 PM, Rich Shepard wrote: > > > On Thu, 1 Feb 2024, MC_Sequoia wrote: > Rich -What happens if you search > on weather underground and then click on > the search result? MC, It loads > just as it has for years. Sonofagun! I had tried entering wunderground.com > in a new tab and that also failed. Strange. Thanks for the pointer. Rich
Re: [PLUG] Weather underground no longer reached by browser
I'm just speculating here, but I'm guessing you might have ran into a stale DNS entry due to some change upstream, etc. Try direct URL again, in guessing your location DNS cache got updated. In the future, don't ping URL, use nslookuo or dig command on wunderground.com. If you can't DNS name resolution to an IP address, then that's what's going on Sent from Proton Mail mobile Original Message On Feb 1, 2024, 2:41 PM, Rich Shepard wrote: > On Thu, 1 Feb 2024, MC_Sequoia wrote: > Rich -What happens if you search on > weather underground and then click on > the search result? MC, It loads just > as it has for years. Sonofagun! I had tried entering wunderground.com in a > new tab and that also failed. Strange. Thanks for the pointer. Rich
Re: [PLUG] Weather underground no longer reached by browser
On Thu, 1 Feb 2024, MC_Sequoia wrote: Rich -What happens if you search on weather underground and then click on the search result? MC, It loads just as it has for years. Sonofagun! I had tried entering wunderground.com in a new tab and that also failed. Strange. Thanks for the pointer. Rich
Re: [PLUG] Weather underground no longer reached by browser
Rich -What happens if you search on weather underground and then click on the search result? Sent from Proton Mail mobile Original Message On Feb 1, 2024, 1:23 PM, Rich Shepard wrote: > I tried refreshing https://www.wunderground.com and both brave and chromium > tell me that URL cannot be reached: Atlanta (404) error code displayed. Yet I > can ping the URL. What might explain this? TIA, Rich
Re: [PLUG] Weather underground no longer reached by browser
On Thu, 1 Feb 2024, Rich Shepard wrote: I tried refreshing https://www.wunderground.com and both brave and chromium tell me that URL cannot be reached: Atlanta (404) error code displayed. Yet I can ping the URL. What might explain this? Strange. I, too, can load it on the mobile phone. Perhaps tomorrow morning it will have recovered from whatever ails it now. Rich
