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]
Ongoing issue that I've experienced in the past. There was some discussion about it in the Mod Transparency Gripe about the Mods thread in Romper. Last I knew, it's a weird DNS thing that isn't hitting enough users to be worthy of further investigation. [Reply]
Originally Posted by Fish:
Ongoing issue that I've experienced in the past. There was some discussion about it in the Mod Transparency thread in Romper I think. Last I knew, it's a weird DNS thing that isn't hitting enough users to be worthy of further investigation.
Looks like it's a bit worse than a few.
It seems like OpenDNS has it cached, which a lot of people use, but 8.8.8.8 is a root DNS server and doesn't know who chiefsplanet.com is. That's not good. [Reply]
Originally Posted by stanleychief:
Looks like it's a bit worse than a few.
It seems like OpenDNS has it cached, which a lot of people use, but 8.8.8.8 is a root DNS server and doesn't know who chiefsplanet.com is. That's not good.
Excellent observation, and would certainly explain my prior issues.
So it looks like the authoritative nameservers are: ns1.monarch17.com and ns2.monarch17.com. Doing an nslookup on the monarch17.com domain fails as well. That probably explains why there is no record of chiefsplanet.com at the moment on the root servers- the authoritative nameservers are not available.
There is a tertiary DNS server, sdns1.ovh.ca, which appears to be up and running, but replies with a SERVFAIL message when querying chiefsplanet.com.
Originally Posted by stanleychief:
So it looks like the authoritative nameservers are: ns1.monarch17.com and ns2.monarch17.com. Doing an nslookup on the monarch17.com domain fails as well. That probably explains why there is no record of chiefsplanet.com at the moment on the root servers- the authoritative nameservers are not available.
There is a tertiary DNS server, sdns1.ovh.ca, which appears to be up and running, but replies with a SERVFAIL message when querying chiefsplanet.com.
Very odd.
there is no mystery why. Any tech, at any level can tell you the name server is not available, you site can’t answer requests to access said site.
Why are the name servers not responding correctly 100% of the time is the root cause to discover. [Reply]
Originally Posted by BigRedChief:
there is no mystery why. Any tech, at any level can tell you the name server is not available, you site can’t answer requests to access said site.
Why are the name servers not responding correctly 100% of the time is the root cause to discover.
Well, if you hit the nameserver by IP, it is available, and has a record of itself:
Code:
; <<>> DiG 9.10.6 <<>> @69.49.245.163 monarch17.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60463
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;monarch17.com. IN A
;; ANSWER SECTION:
monarch17.com. 14400 IN A 69.49.245.163
;; Query time: 48 msec
;; SERVER: 69.49.245.163#53(69.49.245.163)
;; WHEN: Thu Jun 23 23:59:04 CDT 2022
;; MSG SIZE rcvd: 58
However, when you query chiefsplanet from the same server, you get no answer:
Code:
; <<>> DiG 9.10.6 <<>> @69.49.245.163 chiefsplanet.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 65260
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;chiefsplanet.com. IN A
;; Query time: 57 msec
;; SERVER: 69.49.245.163#53(69.49.245.163)
;; WHEN: Thu Jun 23 23:58:24 CDT 2022
;; MSG SIZE rcvd: 45
Gonna have to call you out on statement about 'any tech' being able to tell me about DNS. One phone call to Comcast's or Spectrum's tech support number will disprove that theory. :-) [Reply]
Looks like the clock is on GMT -5 again. I'm guessing someone is doing some work on the server.
If I query the NS servers for monarch17.com on the server itself (69.49.245.163), I see that they are setup for ns1.cprapid.com and ns2.cprapid.com. when querying any other nameserver (Google, OpenDNS, AT&T, Verizon, etc) I don't get any NS record for that domain.
Code:
; <<>> DiG 9.10.6 <<>> @69.49.245.163 monarch17.com NS
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26167
;; flags: qr aa rd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;monarch17.com. IN NS
;; ANSWER SECTION:
monarch17.com. 86400 IN NS ns2.cprapid.com.
monarch17.com. 86400 IN NS ns1.cprapid.com.
;; Query time: 27 msec
;; SERVER: 69.49.245.163#53(69.49.245.163)
;; WHEN: Fri Jun 24 00:27:33 CDT 2022
;; MSG SIZE rcvd: 86
If I look at the history for the monarch17.com domain (@ SecurityTrails.com) I see that the nameservers were listed as GoDaddy (ns75.domaincontrol.com & ns76.domaincontrol.com) which was last seen today. When querying the cprapid.com nameservers, they have no records for monarch17.com. Incidentally, the cprapid.com nameservers are for cpanel. Maybe something trampled the original DNS settings.
It appears that GoDaddy still has A records for the monarch17.com nameservers:
Code:
; <<>> DiG 9.10.6 <<>> @ns75.domaincontrol.com ns1.monarch17.com A
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25719
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 1
;; WARNING: recursion requested but not available
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1472
;; QUESTION SECTION:
;ns1.monarch17.com. IN A
;; ANSWER SECTION:
ns1.monarch17.com. 3600 IN A 69.49.245.163
;; AUTHORITY SECTION:
monarch17.com. 3600 IN NS ns76.domaincontrol.com.
monarch17.com. 3600 IN NS ns75.domaincontrol.com.
;; Query time: 42 msec
;; SERVER: 97.74.107.48#53(97.74.107.48)
;; WHEN: Fri Jun 24 00:55:15 CDT 2022
;; MSG SIZE rcvd: 114
Nope. Why do you ask? I mean, I was doing some client work last night, and ran these checks as I was waiting on other processes to complete. My IP was from my house though (no VPN tunnel). [Reply]
