Re: [Dnsmasq-discuss] DNS/host lookup delay, how to diagnose?
> > Here is the result of a query that took 5 seconds in 'host':- > > > > Feb 20 09:24:05 newdns dnsmasq[465]: 15 192.168.1.92/52420 query[A] > > esprimo.zbmc.eu from 192.168.1.92 > > Feb 20 09:24:05 newdns dnsmasq[465]: 15 192.168.1.92/52420 /etc/hosts > > esprimo.zbmc.eu is 192.168.1.3 > > Feb 20 09:24:06 newdns dnsmasq[465]: 16 192.168.1.92/52342 query[] > > esprimo.zbmc.eu from 192.168.1.92 > > Feb 20 09:24:06 newdns dnsmasq[465]: 16 192.168.1.92/52342 config > > esprimo.zbmc.eu is NODATA-IPv6 ... > > Chart all compoments, shared the new map with us, tell again the situation. Make a "drawing" like * ISP provides DNS at * router is transparent to DNS-traffic * LAN is 192.168.1.0/24 * on that LAN is server "newdns" running Dnsmasq * Dnsmasq is on LAN authoritive for "domain" zbmc.eu * Local dns data comes from * Client that expriences the problem is ... ... * Command to reproduce the problem is ___ * Observations of the problem __ Geert Stappers In an odd way expressing Seen the posting, good luck with describing the problem -- Silence is hard to parse ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] DNS/host lookup delay, how to diagnose?
On Thu, Feb 20, 2020 at 09:54:44AM +, Chris Green wrote: > Here is the result of a query that took 5 seconds in 'host':- > > Feb 20 09:24:05 newdns dnsmasq[465]: 15 192.168.1.92/52420 query[A] > esprimo.zbmc.eu from 192.168.1.92 > Feb 20 09:24:05 newdns dnsmasq[465]: 15 192.168.1.92/52420 /etc/hosts > esprimo.zbmc.eu is 192.168.1.3 > Feb 20 09:24:06 newdns dnsmasq[465]: 16 192.168.1.92/52342 query[] > esprimo.zbmc.eu from 192.168.1.92 > Feb 20 09:24:06 newdns dnsmasq[465]: 16 192.168.1.92/52342 config > esprimo.zbmc.eu is NODATA-IPv6 > Feb 20 09:24:06 newdns dnsmasq[465]: 39 192.168.1.92/52342 query[] > esprimo.zbmc.eu from 192.168.1.92 > Feb 20 09:24:06 newdns dnsmasq[465]: 39 192.168.1.92/52342 config > esprimo.zbmc.eu is NODATA-IPv6 > Feb 20 09:24:11 newdns dnsmasq[465]: 40 192.168.1.92/43165 query[] > esprimo.zbmc.eu from 192.168.1.92 > Feb 20 09:24:11 newdns dnsmasq[465]: 40 192.168.1.92/43165 config > esprimo.zbmc.eu is NODATA-IPv6 > Feb 20 09:24:11 newdns dnsmasq[465]: 41 192.168.1.92/36962 query[MX] > esprimo.zbmc.eu from 192.168.1.92 > Feb 20 09:24:11 newdns dnsmasq[465]: 41 192.168.1.92/36962 config > esprimo.zbmc.eu is NODATA > > So:- > > Why does the query get repeated so many times? Is it because the IPV6 is > failing and > it's retrying? > > Why is there that 5 second delay between 40 and 41? That's presumably > the delay I'm > seeing in the response to the 'host' command. > > Thanks for any explanations and help. Chart all compoments, shared the new map with us, tell again the situation. ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] DNS/host lookup delay, how to diagnose?
On Thu, Feb 20, 2020 at 09:22:05AM +, Chris Green wrote: > > P.S. > > Here is assumed that original poster found in manual page: > > > > --log-queries > > Log the results of DNS queries handled by dnsmasq. > > Yes, thanks, I'll be trying that but I wasn't sure how much timing > information it would provide. > Here is the result of a query that took 5 seconds in 'host':- Feb 20 09:24:05 newdns dnsmasq[465]: 15 192.168.1.92/52420 query[A] esprimo.zbmc.eu from 192.168.1.92 Feb 20 09:24:05 newdns dnsmasq[465]: 15 192.168.1.92/52420 /etc/hosts esprimo.zbmc.eu is 192.168.1.3 Feb 20 09:24:06 newdns dnsmasq[465]: 16 192.168.1.92/52342 query[] esprimo.zbmc.eu from 192.168.1.92 Feb 20 09:24:06 newdns dnsmasq[465]: 16 192.168.1.92/52342 config esprimo.zbmc.eu is NODATA-IPv6 Feb 20 09:24:06 newdns dnsmasq[465]: 17 192.168.1.92/52342 query[] esprimo.zbmc.eu from 192.168.1.92 Feb 20 09:24:06 newdns dnsmasq[465]: 17 192.168.1.92/52342 config esprimo.zbmc.eu is NODATA-IPv6 Feb 20 09:24:06 newdns dnsmasq[465]: 18 192.168.1.92/52342 query[] esprimo.zbmc.eu from 192.168.1.92 Feb 20 09:24:06 newdns dnsmasq[465]: 18 192.168.1.92/52342 config esprimo.zbmc.eu is NODATA-IPv6 Feb 20 09:24:06 newdns dnsmasq[465]: 19 192.168.1.92/52342 query[] esprimo.zbmc.eu from 192.168.1.92 Feb 20 09:24:06 newdns dnsmasq[465]: 19 192.168.1.92/52342 config esprimo.zbmc.eu is NODATA-IPv6 Feb 20 09:24:06 newdns dnsmasq[465]: 20 192.168.1.92/52342 query[] esprimo.zbmc.eu from 192.168.1.92 Feb 20 09:24:06 newdns dnsmasq[465]: 20 192.168.1.92/52342 config esprimo.zbmc.eu is NODATA-IPv6 Feb 20 09:24:06 newdns dnsmasq[465]: 21 192.168.1.92/52342 query[] esprimo.zbmc.eu from 192.168.1.92 Feb 20 09:24:06 newdns dnsmasq[465]: 21 192.168.1.92/52342 config esprimo.zbmc.eu is NODATA-IPv6 Feb 20 09:24:06 newdns dnsmasq[465]: 22 192.168.1.92/52342 query[] esprimo.zbmc.eu from 192.168.1.92 Feb 20 09:24:06 newdns dnsmasq[465]: 22 192.168.1.92/52342 config esprimo.zbmc.eu is NODATA-IPv6 Feb 20 09:24:06 newdns dnsmasq[465]: 23 192.168.1.92/52342 query[] esprimo.zbmc.eu from 192.168.1.92 Feb 20 09:24:06 newdns dnsmasq[465]: 23 192.168.1.92/52342 config esprimo.zbmc.eu is NODATA-IPv6 Feb 20 09:24:06 newdns dnsmasq[465]: 24 192.168.1.92/52342 query[] esprimo.zbmc.eu from 192.168.1.92 Feb 20 09:24:06 newdns dnsmasq[465]: 24 192.168.1.92/52342 config esprimo.zbmc.eu is NODATA-IPv6 Feb 20 09:24:06 newdns dnsmasq[465]: 25 192.168.1.92/52342 query[] esprimo.zbmc.eu from 192.168.1.92 Feb 20 09:24:06 newdns dnsmasq[465]: 25 192.168.1.92/52342 config esprimo.zbmc.eu is NODATA-IPv6 Feb 20 09:24:06 newdns dnsmasq[465]: 26 192.168.1.92/52342 query[] esprimo.zbmc.eu from 192.168.1.92 Feb 20 09:24:06 newdns dnsmasq[465]: 26 192.168.1.92/52342 config esprimo.zbmc.eu is NODATA-IPv6 Feb 20 09:24:06 newdns dnsmasq[465]: 27 192.168.1.92/52342 query[] esprimo.zbmc.eu from 192.168.1.92 Feb 20 09:24:06 newdns dnsmasq[465]: 27 192.168.1.92/52342 config esprimo.zbmc.eu is NODATA-IPv6 Feb 20 09:24:06 newdns dnsmasq[465]: 28 192.168.1.92/52342 query[] esprimo.zbmc.eu from 192.168.1.92 Feb 20 09:24:06 newdns dnsmasq[465]: 28 192.168.1.92/52342 config esprimo.zbmc.eu is NODATA-IPv6 Feb 20 09:24:06 newdns dnsmasq[465]: 27 192.168.1.92/52342 config esprimo.zbmc.eu is NODATA-IPv6 Feb 20 09:24:06 newdns dnsmasq[465]: 28 192.168.1.92/52342 query[] esprimo.zbmc.eu from 192.168.1.92 Feb 20 09:24:06 newdns dnsmasq[465]: 28 192.168.1.92/52342 config esprimo.zbmc.eu is NODATA-IPv6 Feb 20 09:24:06 newdns dnsmasq[465]: 29 192.168.1.92/52342 query[] esprimo.zbmc.eu from 192.168.1.92 Feb 20 09:24:06 newdns dnsmasq[465]: 29 192.168.1.92/52342 config esprimo.zbmc.eu is NODATA-IPv6 Feb 20 09:24:06 newdns dnsmasq[465]: 30 192.168.1.92/52342 query[] esprimo.zbmc.eu from 192.168.1.92 Feb 20 09:24:06 newdns dnsmasq[465]: 30 192.168.1.92/52342 config esprimo.zbmc.eu is NODATA-IPv6 Feb 20 09:24:06 newdns dnsmasq[465]: 31 192.168.1.92/52342 query[] esprimo.zbmc.eu from 192.168.1.92 Feb 20 09:24:06 newdns dnsmasq[465]: 31 192.168.1.92/52342 config esprimo.zbmc.eu is NODATA-IPv6 Feb 20 09:24:06 newdns dnsmasq[465]: 32 192.168.1.92/52342 query[] esprimo.zbmc.eu from 192.168.1.92 Feb 20 09:24:06 newdns dnsmasq[465]: 32 192.168.1.92/52342 config esprimo.zbmc.eu is NODATA-IPv6 Feb 20 09:24:06 newdns dnsmasq[465]: 33 192.168.1.92/52342 query[] esprimo.zbmc.eu from 192.168.1.92 Feb 20 09:24:06 newdns dnsmasq[465]: 33 192.168.1.92/52342 config esprimo.zbmc.eu is NODATA-IPv6 Feb 20 09:24:06 newdns dnsmasq[465]: 34 192.168.1.92/52342 query[] esprimo.zbmc.eu from 192.168.1.92 Feb 20 09:24:06 newdns dnsmasq[465]: 34 192.168.1.92/52342 config esprimo.zbmc.eu is NODATA-IPv6 Feb 20 09:24:06 newdns dnsmasq[465]: 35
Re: [Dnsmasq-discuss] DNS/host lookup delay, how to diagnose?
On Thu, Feb 20, 2020 at 07:36:02AM +0100, Geert Stappers wrote: > On Wed, Feb 19, 2020 at 10:16:17PM +, Chris Green wrote: > > I have a small home LAN with a number of machines running (mostly) > > xubuntu versions 19,10 and 18.04. > > > > I have a local DNS/DHCP server machine (a Raspberry Pi) running dnsmasq. > > ambiguous, Because I can read > > } I have a local DNS/DHCP server machine implemented by running dnsmasq. > } I have a local DNS/DHCP server machine that is also running dnsmasq. > Yes, sorry. 192.168.1.1 - Draytek router with DHCP/DNS turned off. 192.168.1.3 - Desktop running xubuntu 19.10 192.168.1.4 - Raspberry Pi running DHCP and DNS for LAN, Raspbian GNU/Linux, dnsmasq version 2.76 192.168.1.x - Other machines running xubuntu etc. DHCP assigned addresses > > > If I reboot one of my machines and then do a DNS query using 'host' > > for a local machine the first (and only the first) response takes a > > long time. The correct IP address is returned instantly but then > > there is a long (5 seconds) delay before getting back to the command > > prompt. Subsequent searches are much faster. > > Thus the DNS on the Raspberry Pi is providing the initial response to the query but the client's local dnsmasq cache is providing the response to subsequent queries (xubuntu installs dnsmasq for local DNS caching). > > Presumably the faster subsequent responses are down to the local DNS > > cache in the client machine but why am I getting that five second > > delay for the first request? > > > > How can I diagnose this? > > Chart all compoments, shared the new map with us, tell again the situation. > > > Regards > Geert Stappers > > P.S. > Here is assumed that original poster found in manual page: > > --log-queries > Log the results of DNS queries handled by dnsmasq. Yes, thanks, I'll be trying that but I wasn't sure how much timing information it would provide. -- Chris Green ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] DNS/host lookup delay, how to diagnose?
On Wed, Feb 19, 2020 at 10:16:17PM +, Chris Green wrote: > I have a small home LAN with a number of machines running (mostly) > xubuntu versions 19,10 and 18.04. > > I have a local DNS/DHCP server machine (a Raspberry Pi) running dnsmasq. ambiguous, Because I can read } I have a local DNS/DHCP server machine implemented by running dnsmasq. } I have a local DNS/DHCP server machine that is also running dnsmasq. > If I reboot one of my machines and then do a DNS query using 'host' > for a local machine the first (and only the first) response takes a > long time. The correct IP address is returned instantly but then > there is a long (5 seconds) delay before getting back to the command > prompt. Subsequent searches are much faster. > > Presumably the faster subsequent responses are down to the local DNS > cache in the client machine but why am I getting that five second > delay for the first request? > > How can I diagnose this? Chart all compoments, shared the new map with us, tell again the situation. Regards Geert Stappers P.S. Here is assumed that original poster found in manual page: --log-queries Log the results of DNS queries handled by dnsmasq. -- Leven en laten leven ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
[Dnsmasq-discuss] DNS/host lookup delay, how to diagnose?
I have a small home LAN with a number of machines running (mostly) xubuntu versions 19,10 and 18.04. I have a local DNS/DHCP server machine (a Raspberry Pi) running dnsmasq. If I reboot one of my machines and then do a DNS query using 'host' for a local machine the first (and only the first) response takes a long time. The correct IP address is returned instantly but then there is a long (5 seconds) delay before getting back to the command prompt. Subsequent searches are much faster. Presumably the faster subsequent responses are down to the local DNS cache in the client machine but why am I getting that five second delay for the first request? How can I diagnose this? -- Chris Green ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
