On 2026-02-18, Greg Wooledge wrote: > However, I do have a working "reverse DNS" on this host. It was configured > last night (8-9 hours ago); > > $ host 199.231.184.176 > 176.184.231.199.in-addr.arpa domain name pointer wooledge.org.
$ dig +short org. NS d0.org.afilias-nst.org. [...] $ dig +norec @d0.org.afilias-nst.org. wooledge.org ns [...] ;; AUTHORITY SECTION: wooledge.org. 3600 IN NS greg.wooledge.org. wooledge.org. 3600 IN NS remote.wooledge.org. ;; ADDITIONAL SECTION: greg.wooledge.org. 3600 IN A 209.142.155.49 remote.wooledge.org. 3600 IN A 199.231.184.176 [...] $ dig +short @209.142.155.49 remote.wooledge.org. ;; communications error to 209.142.155.49#53: timed out ;; communications error to 209.142.155.49#53: timed out ;; communications error to 209.142.155.49#53: timed out ;; no servers could be reached $ ping 209.142.155.49 PING 209.142.155.49 (209.142.155.49) 56(84) bytes of data. ^C --- 209.142.155.49 ping statistics --- 11 packets transmitted, 0 received, 100% packet loss, time 10232ms You should correct this or find another secondary more available $ dig +short @199.231.184.176 remote.wooledge.org. 199.231.184.176 $ dig +short @199.231.184.176 -x 199.231.184.176 ;; communications error to 199.231.184.176#53: timed out ;; communications error to 199.231.184.176#53: timed out ;; communications error to 199.231.184.176#53: timed out ;; no servers could be reached $ ping 199.231.184.176 PING 199.231.184.176 (199.231.184.176) 56(84) bytes of data. 64 bytes from 199.231.184.176: icmp_seq=1 ttl=51 time=80.9 ms [...] So your DNS do not resolve your IP. Perhaps you filter request from outside ? Or your host/resolv.conf asks your ISP ?
