[Dnsmasq-discuss] editing resolv.conf blocks dnsmasq, but not right away

[Edward McGuire]

> From: Geert Stappers
> Sent: Thursday, March 31, 2022 06:31

> From: Simon Kelley 
> Sent: Thursday, March 31, 2022 08:53

As I feared, I made a clueless error. I created a syslog deadlock.
This is the very case for which the perfectly well documented option
"log-async" exists, and that solved the problem.

Thank you both for responding! Once I ruled out the possibilities
you had me look into, it became easier to see where I actually
erred.

The only part I still don't understand is the 10 to 20 minute delay.

Geert> Most likely due cache content considered valid.

If it were DNS caching in dnsmasq, then when I restart with
cache-size=0, maybe that should eliminate the delay -- instead I
should see the problem instantly. But the behavior stayed the same.
I read syslogd.c, and found no cache code there. The docs on
getnameinfo() claim it does not cache unless you spin up ncsd.

That's where I stopped for now. There's no practical reason now for
me to look any further, just that I don't like mysteries. If time
permits I'll turn on debugging in sysklogd and dnsmasq, and share
what I find.

Cheers
Edward