[Dnsmasq-discuss] Long nslookup times

[Geert Stappers]

On Fri, Mar 02, 2018 at 06:14:33AM +0000, Donald Muller wrote:
> Geert Stappers, Sent Wednesday, February 21, 2018 1:18 PM
> > On Wed, Feb 21, 2018 at 07:02:45PM +0100, Geert Stappers wrote:
> > > On Wed, Feb 21, 2018 at 05:03:34PM +0000, Donald Muller wrote:
> > 
> > 
> > 
> > > > > > > > Wow, a full forty seconds ...
> > > > > > > >
> > > > >
> > > > > I'm not convinced that the culprit is in  dnsmasq.
> > > > > Please continue to find proof  ...
> > 
> > Because you have a interesting probleem ...

Yep

> > > >
> > > > real    0m0.050s
> > > > user    0m0.001s
> > > > sys     0m0.001s
> > 
> > That is much better than forty seconds ...
> > 
> > > > dig is not installed.
> > 
> > Install it. Rule out that we are dealing with a bogus nslookup.
> 
> Results of dig
> 
> [~] # dig www.microsoft.com 192.168.22.220
> ;; ANSWER SECTION:
> www.microsoft.com.      2025    IN      CNAME   www.microsoft.com-c-3.edgekey.net.
> www.microsoft.com-c-3.edgekey.net. 13945 IN CNAME www.microsoft.com-c-3.edgekey.net.globalredir.akadns.net.
> www.microsoft.com-c-3.edgekey.net.globalredir.akadns.net. 72 IN CNAME e13678.dspb.akamaiedge.net.
> e13678.dspb.akamaiedge.net. 19  IN      A       23.206.169.201
> ;; Query time: 10 msec
> 
> ;; ANSWER SECTION:
> 192.168.22.220.         0       IN      A       192.168.22.220
> ;; Query time: 0 msec
> [~] #
> 

Total query time is 10 msec plus 0 msec


@Original Poster:  Come back to the dnsmasq mailinglist
   when you have more proof that your interresting problem
   is caused by dnsmasq.
   If want to hire a consultant, do so.
   If you are here for hiring a consultant, say so.


At least try to understand where to ask what.
Karma bonus points for telling over few weeks
what caused the forty seconds lookup time.


Groeten
Geert Stappers
Probably way too concerned about the health of dnsmasq community
-- 
Leven en laten leven