Subj : Re: ODD DNS behaviour on Pi ZERO W with Bullseye OS
To   : All
From : Lawrence D?Oliveiro
Date : Thu Nov 20 2025 13:30:01

On Wed, 19 Nov 2025 10:33:19 +0000, The Natural Philosopher wrote:

> [/etc/resolv.conf] was set to 127.0.0.1 and IIRC dnsmasq was
> running. I set it to my internal servers that run BIND but I dont
> think its actually using them

dnsmasq by default uses /etc/resolv.conf, unless you point it at
another such file with the --resolv-file option -- obviously you have
to do this to avoid circularity, if dnsmasq is supposed to be the one
handling DNS requests sent to the 127.0.0.1 address.

> So no, I don't know what it is now using as a DNS client.

It is normal for DNS clients to use /etc/resolv.conf. Can?t see any
reason to configure any of them to use some special setting -- apart
of course from a local caching DNS server like dnsmasq, or special DNS
diagnostic tools like dig and host. In other words, everything that
just expects to use the DNS, rather than be part of
administering/troubleshooting the DNS infrastructure, should just be
using /etc/resolv.conf.

> Now unless dig is using some other means than postfix to look up
> DNS, it looks like the problem is in postfix somehow.

dig has nothing to do with Postfix. DNS tools like dig and host
implement their own low-level DNS clients, which can be configured to
do queries in all kinds of ways, precisely to help with
troubleshooting DNS problems.

--- PyGate Linux v1.5
 * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

.