<html><head></head><body><div dir="ltr">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.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Oct 19, 2024 at 9:54 PM チュimoc <<a href="mailto:wzj9912@gmail.com">wzj9912@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">`dig foo.bar @<a href="http://127.0.0.1" target="_blank">127.0.0.1</a> -p 53`, 0ms instant return which upstream is at least 10ms away.<div>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.</div></div>
</blockquote></div>
</body></html>