On Thu, Apr 15, 2021, at 11:00 AM, Jack Craig wrote:
hi list,
so my bind config has apparently not worked despite my dig'ing.
an external config checker says it finds no valid IP' for
linuxlighthouse.com, i am failing http challenge.
Others have given good answers, but let me show you how I parse it...
whois
linuxlighthouse.com | grep ^Name
Name Server:
WS.LINUXLIGHTHOUSE.COM
Name Server:
NS3.ATTDNS.COM
First one is not useful since it lives inside the domain. See:
https://ns1.com/blog/glue-records-and-dedicated-dns
So I check the other one:
dig @NS3.ATTDNS.COM
linuxlighthouse.com any
; <<>> DiG 9.11.28-RedHat-9.11.28-1.fc33 <<>> @NS3.ATTDNS.COM
linuxlighthouse.com any
; (2 servers found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 19251
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;linuxlighthouse.com. IN ANY
;; Query time: 110 msec
;; SERVER: 2001:1890:1c00:5323::c:3#53(2001:1890:1c00:5323::c:3)
;; WHEN: Fri Apr 16 07:59:10 PDT 2021
;; MSG SIZE rcvd: 48
Note the part "WARNING: recursion requested but not available", so it is saying
that it is not authoritative for that domain.
So I check to see that it is the auth for its own domain:
dig @NS3.ATTDNS.COM
ATTDNS.COM any
; <<>> DiG 9.11.28-RedHat-9.11.28-1.fc33 <<>> @NS3.ATTDNS.COM
ATTDNS.COM any
; (2 servers found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 62918
;; flags: qr aa rd; QUERY: 1, ANSWER: 7, AUTHORITY: 0, ADDITIONAL: 9
;; WARNING: recursion requested but not available
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;ATTDNS.COM. IN ANY
;; ANSWER SECTION:
ATTDNS.COM. 28800 IN SOA
ns0.ATTDNS.COM.
eiss-dns.att.COM. 2021033001 3600 1800 2592000
300
ATTDNS.COM. 28800 IN NS
ns1.ATTDNS.COM.
ATTDNS.COM. 28800 IN NS
ns3.ATTDNS.COM.
ATTDNS.COM. 28800 IN NS
ns4.ATTDNS.COM.
ATTDNS.COM. 28800 IN NS
ns2.ATTDNS.COM.
ATTDNS.COM. 600 IN MX 10
mx0b-00191d01.pphosted.COM.
ATTDNS.COM. 600 IN MX 10
mx0a-00191d01.pphosted.COM.
;; ADDITIONAL SECTION:
ns1.ATTDNS.COM. 28800 IN AAAA 2001:1890:1286:320::c:2
ns2.ATTDNS.COM. 28800 IN AAAA 2001:1890:1c00:3320::c:3
ns3.ATTDNS.COM. 28800 IN AAAA 2001:1890:1c00:5323::c:3
ns4.ATTDNS.COM. 28800 IN AAAA 2001:1890:1c00:6320::c:6
ns1.ATTDNS.COM. 28800 IN A 144.160.112.22
ns2.ATTDNS.COM. 28800 IN A 144.160.128.140
ns3.ATTDNS.COM. 28800 IN A 144.160.20.47
ns4.ATTDNS.COM. 28800 IN A 144.160.229.11
;; Query time: 97 msec
;; SERVER: 2001:1890:1c00:5323::c:3#53(2001:1890:1c00:5323::c:3)
;; WHEN: Fri Apr 16 08:00:15 PDT 2021
;; MSG SIZE rcvd: 409
Yup, good there. So you have two name servers listed. We need that glue record to figure
out where one is and the other claims to not know who you are.
--
Doug Herr
fedoraproject.org(a)wombatz.com