"Oops! we ran into some problems"

Nope no cloudflare here... I think the outside DNS servers are looking for an update and our servers are not sending them out in time. (Again ust a guess.)
Unless the IP addresses are changing with each TTL expiration, I'm not sure that should matter. DNS isn't typically a resource-intensive activity.

My Cloudflare reference was based on their proxied IP addressing that I've had considerable trouble with.
 
  • Like
Reactions: charlesrshell
While Foxbats issue was self inflicted, it gave me an idea
Glad my faux pas could help out! ;)

I figured out that the IPv6 sites were okay (Google, Apple, Bing) because my IPv6 settings weren’t changed from DHCP. It was just the IPv4 sites. Does (should) SatelliteGuys.US support IPv6?
 
  • Like
Reactions: charlesrshell
Another blip out at 1:31, took 2 minutes before a post I made showed up.

I have been get a lot of these, where these little blips keep happening for 1-2 minutes, while it is happening, I will check another site on a new tab, loads fine.
 
Another blip out at 1:31, took 2 minutes before a post I made showed up.

I have been get a lot of these, where these little blips keep happening for 1-2 minutes, while it is happening, I will check another site on a new tab, loads fine.
That may have been me working on the no reply issue. I forgot to clear one of the other caches. Need to make sure we got them all. I forget at times we use a total of 3 different CDN's for caching.