[Dnsmasq-discuss] Bug? no-negcache set but still instant status:REFUSE w/ EDE: 23 (Network Error).

[seizing-rinse-poem at duck.com]

I guess, for now, it is dns-forward-max hit. And the counter never gets
reset and/or the connections to upstream never get timeout/flushed because
the REFUSED reply lasted much longer than 40s(the timeout in source code)
while no request going in for that period.

On Sat, Oct 19, 2024 at 9:54 PM チュimoc <wzj9912 at gmail.com> wrote:

> `dig foo.bar @127.0.0.1 -p 53`, 0ms instant return which upstream is at
> least 10ms away.
> But dig upstream the result is correct. Restarted dnsmasq it'll work for a
> while then error again. I'm on the latest git. Running a debug screen for
> now and want to get more info from dev.
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/attachments/20241019/e067cc6c/attachment.htm>