On Wed, Feb 18, 2026 at 23:08:37 +0100, Michel Verdier wrote: > ;; ADDITIONAL SECTION: > greg.wooledge.org. 3600 IN A 209.142.155.49 > remote.wooledge.org. 3600 IN A 199.231.184.176 > [...] > > You should correct this or find another secondary more available
Fair point. The 209 address was my home system's static IP address for several years, but after the switch from DSL to fiber Internet, I no longer have a static IP at home. This complicates things. The registrar won't let me simply remove the second DNS server. They want two. So, I guess the *least difficult* path is to run the secondary DNS on my non-static-addressed home system, the same way I used to run it on my static-addressed home system in the past. I've got some infrastructure in place to update DNS on the remote VPS with my home IP address when it changes, but it'll need a minor tweak to update the instance on my home system as well, so they remain in sync. I believe I've successfully updated the "glue" records on the registrar's web site, but it will take time to propagate. > $ 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 > > So your DNS do not resolve your IP. Perhaps you filter request from > outside ? Or your host/resolv.conf asks your ISP ? I'm not authoritative for the reverse lookup. On Wed, Feb 18, 2026 at 23:25:25 +0100, Michel Verdier wrote: > On 2026-02-18, Michel Verdier wrote: > some wrong things > > $ dig -x 199.231.184.176 > ;; communications error to ::1#53: timed out > ;; communications error to ::1#53: timed out > ;; communications error to ::1#53: timed out > ;; communications error to 127.0.0.1#53: timed out > So it seems that you correctly set a reverse. But there is a timeout > during revolving. You should tell this to your provider. I'll take that under advisement, I suppose.
