On 2023-05-09 20:42, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-05-09 16:46, Per Jessen wrote:
Carlos E. R. wrote:
I just want dnsmasq to process and answer all queries, not a backup or external resolver.
That is _exactly_ what it does in the config I posted above:
search local.net z.local.net i.local.net nameserver 127.0.0.1 nameserver 192.168.2.254 nameserver 2001:db8:4c68:1::1000
You mean that all those IPs are the same single machine, 127.0.0.1?
No - 127.0.0.1 is the local host, inserted by netconfig, with dnsmasq listening, but the other two are indeed just one machine, our core DNS, supplied by dhcp/RA.
With that config, dnsmasq processes and answers all queries which is what you said you want.
Ok. But if dnsmasq fails, then the other servers will be queried instead, silently, so the failure of dnsmasq is not noticed. In a server I probably should want that, but not on a desktop machine. I prefer it to fail so that I know.
Because that is not what I get when I leave it to automatics. I get there the DNSs the router says. I do not want what the router says.
Oh. Well, I do, otherwise dnsmasq will not have any forwarders.
Yet you conclude the machines are all wrong ... it can't be some common factor.
"The behaviour" is about the resolv.conf rotating fast.
Yes, and you blame all of your machines and chose to ignore the one common factor - a factor:
a) you have no control over and b) known to exhibit odd behaviour.
You forget that the machines that use NM do not exhibit the problem, despite using the same crap router.
No, but you have perhaps forgotten that dnsmasq on that machine uses a different config. afair, it does not look at /etc/resolv.conf.
Correct, it looks at /run/NetworkManager/no-stub-resolv.conf. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)