That's not a DNS error. That's and SSL Certificate Error.It happened again about 8:59 PM. DNS servers 8.8.8.8 and 1.1.1.1 both report the correct address.
I did catch this error so looks like some part of the configuration of the hosting xenforo.cloud environment.
Dave
View attachment 685097
I am now seeing 2 different IPs bouncing around the DNS Servers if I check often.
> disboards.com
Server: dnsr1.sbcglobal.net
Address: 68.94.156.1
Non-authoritative answer:
Name: disboards.com
Address: 108.171.164.208
> server 1.1.1.1
Default Server: one.one.one.one
Address: 1.1.1.1
> disboards.com
Server: one.one.one.one
Address: 1.1.1.1
Non-authoritative answer:
Name: disboards.com
Address: 108.61.75.210
Dave
We know that but our client computers don't use those DNS servers. I am also seeing something odd based on what I perform a nslookup against.Those are just the DNS servers that your ISP uses. They are non-authoritative.
The authoritative ones are...
We know that but our client computers don't use those DNS servers. I am also seeing something odd based on what I perform a nslookup against.
disboards.com always appears to work for 108.61.75.210 but www.disboards.com seems to like to switch to Address: 108.171.164.208. The wrong IP from time to time.
Here is an example:
> www.disboards.com
Server: dns.google
Address: 8.8.8.8
Non-authoritative answer:
Name: www.disboards.com
Address: 108.61.75.210
> www.disboards.com
Server: dns.google
Address: 8.8.8.8
Non-authoritative answer:
Name: www.disboards.com
Address: 108.61.75.210
> www.disboards.com
Server: dns.google
Address: 8.8.8.8
Non-authoritative answer:
Name: www.disboards.com
Address:
> www.disboards.com
Server: dns.google
Address: 8.8.8.8
Non-authoritative answer:
Name: www.disboards.com
Address: 108.61.75.210
> www.disboards.com
Server: dns.google
Address: 8.8.8.8
Non-authoritative answer:
Name: www.disboards.com
Address: 108.61.75.210
> www.disboards.com
Server: dns.google
Address: 8.8.8.8
Non-authoritative answer:
Name: www.disboards.com
Address: 108.171.164.208
Dave
Yes, that one is coming out of Russia when I do a global DNS check...Oh wow! Yea, that's odd. I just tried a reverse lookup on 108.171.164.208 and nothing was found.
That would certainly explain the site not available errors.
Orphan record on one of the DNS servers?
It is not just one DNS server. I see it on multiple major servers that show 108.171.164.208 intermittently which is a major glitch for the Disboards.com forums.Oh wow! Yea, that's odd. I just tried a reverse lookup on 108.171.164.208 and nothing was found.
That would certainly explain the site not available errors.
Orphan record on one of the DNS servers?
Well, I mean isn't that how DNS Cache Poisoning works? It keeps spreading to all DNS Caches that request the lookup and you can't get rid of it until the TTL's expire.It is not just one DNS server. I see it on multiple major servers that show 108.171.164.208 intermittently which is a major glitch for the Disboards.com forums.
Cloudflare - 1.1.1.1
Google - 8.8.8.8
AT&T - 68.94.156.1
A few don't seem to fail so far in my testing:
Level 3 - 4.2.2.1
Quad9 - 9.9.9.9
Cisco Cloud Umbrella Security - 208.67.222.222
Dave
That’s why I mentioned them before. All of those transactions are time sensitive and I can’t imagine how frustrating trying to negotiate a rental or trade would be if both parties kept getting booted intermittently.Thanks for pushing them. Praying they figure this out soon!
Just got back on. Locked out since 10 pm Eastern last night. R/T Boards really backed up!
Thanks for keeping us updated...I just spent half an hour on the phone with them again and they swear it will be fixed in 4 hours. You'll have to excuse me for having doubts
It is not really poisoning the DNS since it is just the old IP keeping popping up. It is not a random hijack which would be a complete redirection to a malicious address.Well, I mean isn't that how DNS Cache Poisoning works? It keeps spreading to all DNS Caches that request the lookup and you can't get rid of it until the TTL's expire.
That’s why I mentioned them before. All of those transactions are time sensitive and I can’t imagine how frustrating trying to negotiate a rental or trade would be if both parties kept getting booted intermittently.
Gotcha. I didn't realize it was the old IP Address. I guess I thought someone had said that the IP originated in Russia. Sorry for my confusion.It is not really poisoning the DNS since it is just the old IP keeping popping up. It is not a random hijack which would be a complete redirection to a malicious address.
More of a bug / human error in a very old but complex DNS scheme. Everyone starts pointing fingers up and down the chain.
Dave
Dunno, but I’m kinda glad they stopped. Deleting 40 or 50 emails every day gets old.Could this problem be related to no longer receiving emails for threads I'm watching? I stopped receiving those 2 or 3 days ago too.
Might be. I tried to use my phone to access the DIS using data instead of wi-fi and never got the email with the code (for two-step authentication).Could this problem be related to no longer receiving emails for threads I'm watching? I stopped receiving those 2 or 3 days ago too.