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.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.)
Glad my faux pas could help out!While Foxbats issue was self inflicted, it gave me an idea
Yep, longer clocking times for things like that. I also see it.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.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.