ok, now we are getting somewhere!
So of the two servers that are listed the primary one, mine, does not respond
the secondary from AT&T is not responsive
finally as you'll see below pinging t
Internal DNS is being returned as the external DNS number, that's a third thing I need to fix up.
So I need to find out what's the correct AT&T DNS reference that I should be using and second I need to fix my own DNS so that I return the external not the internal IP
Retest with improved DNS parsing method, thx again..
ping -c 3 108.220.213.121 PING 108.220.213.121 (108.220.213.121) 56(84) bytes of data. 64 bytes from 108.220.213.121: icmp_seq=1 ttl=64 time=1.51 ms 64 bytes from 108.220.213.121: icmp_seq=2 ttl=64 time=0.850 ms 64 bytes from 108.220.213.121: icmp_seq=3 ttl=64 time=1.35 ms
--- 108.220.213.121 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 0.850/1.236/1.513/0.281 ms [jackc@ws ~ $ ping -c 3 ns3.attdns.com PING ns3.attdns.com (144.160.20.47) 56(84) bytes of data.
--- ns3.attdns.com ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2038ms
*[jackc@ws ~ $ ping -c 3 ws.linuxlighthouse.com http://ws.linuxlighthouse.comPING ws (10.0.0.101) 56(84) bytes of data.64 bytes from ws (10.0.0.101): icmp_seq=1 ttl=64 time=0.083 ms64 bytes from ws (10.0.0.101): icmp_seq=2 ttl=64 time=0.062 ms64 bytes from ws (10.0.0.101): icmp_seq=3 ttl=64 time=0.067 ms*
*wrong!! let me clean these up and see how far that gets me *
*thanks again for all your help *
*I am getting there slow but sure*
--- ws ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2038ms rtt min/avg/max/mdev = 0.062/0.070/0.083/0.009 ms
On Fri, Apr 16, 2021 at 8:25 AM Doug H. fedoraproject.org@wombatz.com wrote:
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@wombatz.com _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure