On 14/3/23 06:14, local10 wrote:
Strangely, the issue resolved itself without me having to do anything. Am really puzzled as to what it was. Perhaps the internet provider suddenly started to block DNS queries but then allowed them again? If so, why did dig's message say that there was "communications error to 127.0.0.1#53: timed out"? It really gives an impression that dig was failing to connect 127.0.0.1 port 53, on which bind was running. # dig www.yahoo.com <http://www.yahoo.com> ;; communications error to 127.0.0.1#53: timed out ;; communications error to 127.0.0.1#53: timed out ... Maybe someone will shed some light on this. Thanks to everyone who responded.
I had a signed DNS error in a similar configuration using a bind authoritive and caching server. It turned out it was systemd-resolved interfering and/or replacing part of the DNS chain
FYI systed-resolved is the inbuilt debian caching DNS server which may be enabled by default. If you run that you don't need a bind9 caching name server
What does this report ? systemctl status systemd-resolved If there is anything there at all, check logs. You may find something -- Jeremy (Lists)
