<div dir="ltr"><div><div><div>HI<br><br></div>I am upgrading the dnsmasq now, But I have couple of more question, I read somewhere, dnsmasq can cache only A, AAAA records only.. is that true?? and multiple line caching is not supported. Is there anyway we can cache the TCP query??<br><br></div>Regards<br></div>Harish Shetty<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 9, 2018 at 1:42 AM, Simon Kelley <span dir="ltr"><<a href="mailto:simon@thekelleys.org.uk" target="_blank">simon@thekelleys.org.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Check all the servers you have configured. If one is not accepting TCP<br>
connections, that could delay things whilst the connection attempt times<br>
out.<br>
<br>
If the upstream servers accept TCP connections and reply on them in a<br>
timely manner, I don't know what else could be causing the problem. It<br>
would be worth setting --log-queries to try and see where the delays are.<br>
<br>
2.48 is very, very old. Can you upgrade?<br>
<br>
<br>
Cheers,<br>
<br>
Simon.<br>
<br>
On 07/05/18 15:30, Harish Shetty wrote:<br>
> Hi Simon<br>
> <br>
> Thanks for the reply, Yes you are rite, Truncated bit is set in the<br>
> message. I am seeing ";; Truncated, retrying in TCP mode." in the<br>
> answer. But it is expected and answer is more than 512 bytes (which is<br>
> size of UDB packet). TCP port 53 is allowed , but DNS respone time from<br>
> dnsmasq service is more than 3 sec sometime 4 or 5 sec. When we query<br>
> directly upstream server we are seeing the response on avg of 100 to<br>
> 200 ms.<br>
> <br>
> Is there anyway we can make DNS query faster in dnsmasq server, because<br>
> it is making our application timeouts.<br>
> <br>
> Regards<br>
> Harish Shetty<br>
> <br>
> On Mon, May 7, 2018 at 7:03 PM, Simon Kelley <<a href="mailto:simon@thekelleys.org.uk">simon@thekelleys.org.uk</a><br>
> <mailto:<a href="mailto:simon@thekelleys.org.uk">simon@thekelleys.org.<wbr>uk</a>>> wrote:<br>
> <br>
> That's large enough to need TCP.<br>
> <br>
> What I'd expect top happen is that the upstream server returns an answer<br>
> with the truncated bit setin the header. This answer gets returned by<br>
> dnsmasq to the original requestor. The original requestor makes a TCP<br>
> connection to dnsmasq and re-sends the query. Dnsmasq makes a TCP<br>
> connection upstream and send the query, and gets the result. It then<br>
> send the result back down the TCP connection to the original requestor.<br>
> <br>
> Anything blocking or distrupting TCP connections on port 53 is suspect.<br>
> An non-responsive upstream server will cause delays whilst the<br>
> connection times out.<br>
> <br>
> Try running the query direct to the upstream servers using dig +vc<br>
> <br>
> Cheers,<br>
> <br>
> Simon.<br>
> <br>
> <br>
> On 07/05/18 13:57, Harish Shetty wrote:<br>
> > Hi All<br>
> ><br>
> > I am facing some issue with dnsmasq. Currently I am using<br>
> dnsmasq-2.48<br>
> > , I am using this as my forwarder and caching sever. But my<br>
> problem is,<br>
> > when i query for a high payload SRV record (answer size is about 3500<br>
> > bytes) response time some times crosses 4000ms, and intermittently<br>
> timeout.<br>
> ><br>
> > I have tried enabling the logquries, but it didnt give much<br>
> information<br>
> > to me, Any suggestion on the debugging or more details will be<br>
> helpful<br>
> ><br>
> > Regards<br>
> > Harish Shetty<br>
> ><br>
> ><br>
> ><br>
> ><br>
> > ______________________________<wbr>_________________<br>
> > Dnsmasq-discuss mailing list<br>
> > <a href="mailto:Dnsmasq-discuss@lists.thekelleys.org.uk">Dnsmasq-discuss@lists.<wbr>thekelleys.org.uk</a><br>
> <mailto:<a href="mailto:Dnsmasq-discuss@lists.thekelleys.org.uk">Dnsmasq-discuss@lists.<wbr>thekelleys.org.uk</a>><br>
> > <a href="http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss" rel="noreferrer" target="_blank">http://lists.thekelleys.org.<wbr>uk/mailman/listinfo/dnsmasq-<wbr>discuss</a><br>
> <<a href="http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss" rel="noreferrer" target="_blank">http://lists.thekelleys.org.<wbr>uk/mailman/listinfo/dnsmasq-<wbr>discuss</a>><br>
> ><br>
> <br>
> ______________________________<wbr>_________________<br>
> Dnsmasq-discuss mailing list<br>
> <a href="mailto:Dnsmasq-discuss@lists.thekelleys.org.uk">Dnsmasq-discuss@lists.<wbr>thekelleys.org.uk</a><br>
> <mailto:<a href="mailto:Dnsmasq-discuss@lists.thekelleys.org.uk">Dnsmasq-discuss@lists.<wbr>thekelleys.org.uk</a>><br>
> <a href="http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss" rel="noreferrer" target="_blank">http://lists.thekelleys.org.<wbr>uk/mailman/listinfo/dnsmasq-<wbr>discuss</a><br>
> <<a href="http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss" rel="noreferrer" target="_blank">http://lists.thekelleys.org.<wbr>uk/mailman/listinfo/dnsmasq-<wbr>discuss</a>><br>
> <br>
> <br>
</blockquote></div><br></div>