I tried to load up the site and got a message that chiefsplanet.com was not found. Did a DNS lookup and got the same. Did someone hijack the domain, or was something removed that shouldn't have been?
I added a DNS entry in my hosts file to get here. [Reply]
Originally Posted by DaFace:
Wonder if Kyle is self-hosting DNS for some reason. Unfortunately he's the only one with access to those kinds of functions.
Total speculation here, but if you do a reverse lookup on Chiefsplanet's IP address (you'd have to use https://securitytrails.com or similar to do this since DNS is now hosed), I see several indications that this is hosted on CPanel. If I recall (it's been many years ago) I think those usually work better when they can self-manage their own DNS entries.
With the last NS records indicating that monarch17.com was the nameserver, and with monarch17.com now pointing to a CPanel DNS server, I'd say it's probably likely monarch17.com is self-hosted on a system running CPanel. [Reply]
Originally Posted by stanleychief:
Total speculation here, but if you do a reverse lookup on Chiefsplanet's IP address (you'd have to use https://securitytrails.com or similar to do this since DNS is now hosed), I see several indications that this is hosted on CPanel. If I recall (it's been many years ago) I think those usually work better when they can self-manage their own DNS entries.
With the last NS records indicating that monarch17.com was the nameserver, and with monarch17.com now pointing to a CPanel DNS server, I'd say it's probably likely monarch17.com is self-hosted on a system running CPanel.
Originally Posted by Hank Hill:
I have no idea what is being discussed in here.
Non-technical version:
In a nutshell, there is something broken, that if not fixed, will lead to the site being unavailable to everyone.
If you are in anyway curious what DNS is, look here
More technical:
The people still able to view this site are using DNS servers that still have the A record cached for chiefsplanet.com. When that expires, the site will also be unavailable to them as well. OpenDNS for instance, which is very popular, is still providing the correct IP address for this site. Here's a brief explanation about why: https://www.opendns.com/opendns-smartcache/ It is also possible that mobile apps and some browsers also cache the DNS record for a while longer than the stated TTL. As those also expire, and they re-query, the site will also fail to load. [Reply]
Originally Posted by stanleychief: Non-technical version:
In a nutshell, there is something broken, that if not fixed, will lead to the site being unavailable to everyone.
If you are in anyway curious what DNS is, look here
More technical:
The people still able to view this site are using DNS servers that still have the A record cached for chiefsplanet.com. When that expires, the site will also be unavailable to them as well. OpenDNS for instance, which is very popular, is still providing the correct IP address for this site. Here's a brief explanation about why: https://www.opendns.com/opendns-smartcache/ It is also possible that mobile apps and some browsers also cache the DNS record for a while longer than the stated TTL. As those also expire, and they re-query, the site will also fail to load.
Y2K all over again!!!!!! RUUUUUUUUUUUUUUUUN [Reply]
