<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>I think these kinds of problem arises usually when connectivity
to upstream is broken or interrupted.</p>
<p>150 is number of concurrent queries waiting for resolution. It
should not be required to increase this limit if the remote server
is answering fast. Unless I am mistaken, as soon as the response
arrives back, that frees on of those sessions. Dnsmasq cannot
drive retries itself, it relies on client to do them. But that
should not matter.</p>
<p>Unless we know more details when and how increasing this value
should help, I would be opposed in doing so. We may need to
improve switching to alternative resolvers, if that alternatives
respond faster. If that is interruption in upstream connectivity,
no increase here would help.<br>
</p>
<div class="moz-cite-prefix">On 29. 06. 23 15:39, Eric Fahlgren
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAP2Qz+XgKpZXg=MKSR4Q61mY4XfYsj-x6EeSY6Hhx+0VpeAb2Q@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Jun 29, 2023 at
12:52 AM Buck Horn <<a
href="mailto:buckhorn@weibsvolk.org"
moz-do-not-send="true" class="moz-txt-link-freetext">buckhorn@weibsvolk.org</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">
Blindly increasing dns-forward-max without having analysed
the actual <br>
issue does not seem to recommend itself as the best option
available to <br>
me, even if it would turn out that actual resource impacts
are minor.<br>
<br>
Stopping or unconfiguring the DNS loop or switching to more
reliable <br>
upstreams would seem more adequate measures to address the
warning.<br>
<br>
If you have actively been involved in investigating such an
issue, it <br>
may be worth verifying those causes, if only to preclude
them. ;)<br>
</blockquote>
<div><br>
</div>
<div style="font-family:arial,sans-serif;color:rgb(0,0,0)"
class="gmail_default">Hi Buck,</div>
<div style="font-family:arial,sans-serif;color:rgb(0,0,0)"
class="gmail_default"><br>
</div>
<div style="font-family:arial,sans-serif;color:rgb(0,0,0)"
class="gmail_default">Thanks a bunch for the possible
causes. As you could probably tell from my "assuming", I
have not done any root cause investigation, all the reports
are just anecdotal "I saw this, then did that, and the issue
went away..." In some of the posts, it has been suggested
that the installation default be raised to 500 based on
these reports, because "why not?" and "it looks like it
fixes something?"<br>
</div>
<div style="font-family:arial,sans-serif;color:rgb(0,0,0)"
class="gmail_default"><br>
</div>
<div style="font-family:arial,sans-serif;color:rgb(0,0,0)"
class="gmail_default">So, at this point I'm still in
tentative data collection phase and armed with your
suggested avenues of investigation, I'll see if I can get
someone to reproduce the problem and find the real root
issue.</div>
<div style="font-family:arial,sans-serif;color:rgb(0,0,0)"
class="gmail_default"><br>
</div>
<div style="font-family:arial,sans-serif;color:rgb(0,0,0)"
class="gmail_default">Thanks again,</div>
<div style="font-family:arial,sans-serif;color:rgb(0,0,0)"
class="gmail_default">Eric<br>
</div>
</div>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Dnsmasq-discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Dnsmasq-discuss@lists.thekelleys.org.uk">Dnsmasq-discuss@lists.thekelleys.org.uk</a>
<a class="moz-txt-link-freetext" href="https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss">https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss</a>
</pre>
</blockquote>
<pre class="moz-signature" cols="72">--
Petr Menšík
Software Engineer, RHEL
Red Hat, <a class="moz-txt-link-freetext" href="http://www.redhat.com/">http://www.redhat.com/</a>
PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB</pre>
</body>
</html>