Quoting fsmithred (fsmithred@???):

> nslookup, ping, traceroute all fail on tracker.dyne.org

At the risk of belabouring the obvious (but because some folks
may not know the implication), above is because tracker.dyne.org is
currently status NXDOMAIN (meaning: not defined in the authoritative
DNS). So, someone fumble-fingered a zonefile edit?


Liten-Datamaskin:~ rick$ dig -t ns dyne.org +short
ns4.dyne.org.
ns6.gandi.net.
ns2.dyne.org.
Liten-Datamaskin:~ rick$ dig -t a tracker.dyne.org @ns4.dyne.org +short
Liten-Datamaskin:~ rick$ dig -t a tracker.dyne.org @ns4.dyne.org

; <<>> DiG 9.10.6 <<>> -t a tracker.dyne.org @ns4.dyne.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 22020
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;tracker.dyne.org.        IN    A

;; AUTHORITY SECTION:
dyne.org.        900    IN    SOA    ns4.dyne.org. hostmaster.dyne.org.
2020122200 7200 3600 86400 900

;; Query time: 189 msec
;; SERVER: 135.181.111.28#53(135.181.111.28)
;; WHEN: Sat Jan 16 15:36:13 PST 2021
;; MSG SIZE rcvd: 96

Liten-Datamaskin:~ rick$

-- 
Cheers,                                     "I have neither the time nor the 
Rick Moen                                   crayons to explain this to you."
rick@???                                 -- Seen on StackOverflow
McQ! (4x80)