Re: [Dnsmasq-discuss] Long nslookup times
Geert, Apologies if offended you in some way by emailing this list about some strange behavior I noticed when testing my dnsmasq setup. I admit that my Linux skills aren't strong but I am not looking for a consultant. What I was looking for was some assistance in determining whether the issue was with dnsmasq itself, my setup/configuration of dnsmasq, or somewhere else in which case I would bother someone else. Thanks for your assistance so far. If anyone else would like offer suggestions please do. Recap 2 computers on the same network. One running Windows server 2012 R2 with Microsoft DNS and DHCP and the other one a QNAP NAS running dnsmasq. Both connected to the same switch and both versions of DNS pointing to the same upstream DNS server which is my router which is not running DNS but just forwards the requests to my ISP DNS servers. The network is 1GB and there is not a lot of N/W traffic. A nslookup of www.microsoft.com using dnsmasq takes 40 seconds. The same lookup using the Microsoft DNS takes less than a second. Thanks Don > @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 > > ___ > Dnsmasq-discuss mailing list > Dnsmasq-discuss@lists.thekelleys.org.uk > http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] Long nslookup times
On Fri, Mar 02, 2018 at 06:14:33AM +, 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 +, 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 > > > > > > > > real0m0.050s > > > > user0m0.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. 2025IN 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 ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] Long nslookup times
> -Original Message- > From: Dnsmasq-discuss [mailto:dnsmasq-discuss- > boun...@lists.thekelleys.org.uk] On Behalf Of Geert Stappers > Sent: Wednesday, February 21, 2018 1:18 PM > To: dnsmasq-discuss@lists.thekelleys.org.uk > Subject: Re: [Dnsmasq-discuss] Long nslookup times > > On Wed, Feb 21, 2018 at 07:02:45PM +0100, Geert Stappers wrote: > > On Wed, Feb 21, 2018 at 05:03:34PM +, Donald Muller wrote: > > > > > > On Wed, Jan 31, 2018 at 10:22:53AM +0100, Geert Stappers wrote: > > > > > > > On Tue, Jan 30, 2018 at 05:08:05PM +, Donald Muller wrote: > > > > > > > > > > > > > > > > Using Microsoft DNS server [~] # time nslookup > > > > > > > > www.microsoft.com 192.168.22.200 Address 1: > > > > > > > > 192.168.22.200 djmfs1.djmuller.com > > > > > > > > > > > > > > Programm nslookup did a reverse lookup on used DNS address > > > > > > > and got back a FQDN > > > > > > > > > > > > > > > Using dnsmasq > > > > > > > > [~] # time nslookup www.microsoft.com 192.168.22.220 Address > 1: > > > > > > > > 192.168.22.220 DJMFS2 > > > > > > > > > > > > > > Non Fully Qualified Domain Name for the used DNS address > > So we know that the reverse DNS data source is some what sloppy > configured. > > ||| 192.168.22.200 djmfs1.djmuller.com > ||| 192.168.22.220 DJMFS2 > > But the real thing I'm trying to tell: extra (unwanted??) reverse lookup > happen > > > > > > > > > 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 ... > > > > > > > > > > What additional information do you need? > > > > > All devices, including the router, are connected at 1GB to a switch. > > > > > > > > The testclient what does it have in /etc/resolv.conf while testing? > > > > Other tools for `nslookup`, such as `dig` and `host`, what timing > > > > results have those? > > > > The QNAP NAS with dnsmasq, how much traffic must it handle? > > > > > > The test client has the following in reslov.conf > > > > > > [~] # cat /etc/resolv.conf > > > nameserver 192.168.22.220 > > > nameserver 192.168.22.242 > > > > > > host shows the following: > > > > > > [~] # time host www.microsoft.com 192.168.22.220 Using domain > > > server: > > > Name: 192.168.22.220 > > > Address: 192.168.22.220#53 > > > Aliases: > > > > > > www.microsoft.com is an alias for www.microsoft.com-c-3.edgekey.net. > > > www.microsoft.com-c-3.edgekey.net is an alias for www.microsoft.com- > c-3.edgekey.net.globalredir.akadns.net. > > > www.microsoft.com-c-3.edgekey.net.globalredir.akadns.net is an alias > for e13678.dspb.akamaiedge.net. > > > e13678.dspb.akamaiedge.net has address 104.88.47.193 > > > e13678.dspb.akamaiedge.net has IPv6 address 2001:418:143c:19e::356e > > > e13678.dspb.akamaiedge.net has IPv6 address 2001:418:143c:1a9::356e > > > > > > real0m0.050s > > > user0m0.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 ; <<>> DiG 9.11.2 <<>> www.microsoft.com 192.168.22.220 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 54000 ;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1280 ;; QUESTION SECTION: ;www.microsoft.com. IN A ;; ANSWER SECTION: www.microsoft.com. 2025IN 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 ;; SERVER: 192.168.22.220#53(192.168.22.220) ;; WHEN: Fri Mar 02 01:13:06 EST 2018 ;; MSG SIZE rcvd: 213 ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2
Re: [Dnsmasq-discuss] Long nslookup times
On Wed, Feb 21, 2018 at 07:02:45PM +0100, Geert Stappers wrote: > On Wed, Feb 21, 2018 at 05:03:34PM +, Donald Muller wrote: > > > > > On Wed, Jan 31, 2018 at 10:22:53AM +0100, Geert Stappers wrote: > > > > > > On Tue, Jan 30, 2018 at 05:08:05PM +, Donald Muller wrote: > > > > > > > > > > > > > > Using Microsoft DNS server > > > > > > > [~] # time nslookup www.microsoft.com 192.168.22.200 Address 1: > > > > > > > 192.168.22.200 djmfs1.djmuller.com > > > > > > > > > > > > Programm nslookup did a reverse lookup on used DNS address and got > > > > > > back a FQDN > > > > > > > > > > > > > Using dnsmasq > > > > > > > [~] # time nslookup www.microsoft.com 192.168.22.220 Address 1: > > > > > > > 192.168.22.220 DJMFS2 > > > > > > > > > > > > Non Fully Qualified Domain Name for the used DNS address So we know that the reverse DNS data source is some what sloppy configured. ||| 192.168.22.200 djmfs1.djmuller.com ||| 192.168.22.220 DJMFS2 But the real thing I'm trying to tell: extra (unwanted??) reverse lookup happen > > > > > > 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 ... > > > > > > > What additional information do you need? > > > > All devices, including the router, are connected at 1GB to a switch. > > > > > > The testclient what does it have in /etc/resolv.conf while testing? > > > Other tools for `nslookup`, such as `dig` and `host`, what timing results > > > have > > > those? > > > The QNAP NAS with dnsmasq, how much traffic must it handle? > > > > The test client has the following in reslov.conf > > > > [~] # cat /etc/resolv.conf > > nameserver 192.168.22.220 > > nameserver 192.168.22.242 > > > > host shows the following: > > > > [~] # time host www.microsoft.com 192.168.22.220 > > Using domain server: > > Name: 192.168.22.220 > > Address: 192.168.22.220#53 > > Aliases: > > > > www.microsoft.com is an alias for www.microsoft.com-c-3.edgekey.net. > > www.microsoft.com-c-3.edgekey.net is an alias for > > www.microsoft.com-c-3.edgekey.net.globalredir.akadns.net. > > www.microsoft.com-c-3.edgekey.net.globalredir.akadns.net is an alias for > > e13678.dspb.akamaiedge.net. > > e13678.dspb.akamaiedge.net has address 104.88.47.193 > > e13678.dspb.akamaiedge.net has IPv6 address 2001:418:143c:19e::356e > > e13678.dspb.akamaiedge.net has IPv6 address 2001:418:143c:1a9::356e > > > > real0m0.050s > > user0m0.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. > > > > The QNAP NAS is not handling much traffic. If is a home file server with > > minimal traffic. > > > > I also set up dnsmasq on a second NAS with just DNS running, no DHCP. This > > NAS is used for backups so normally has no traffic. I get the same long > > times > > > > [~] # time nslookup www.microsoft.com 192.168.22.242 > > Server:192.168.22.242 > > Address 1: 192.168.22.242 djmfs3.djmuller.com A reverse DNS lookup was performed > > > > Name: www.microsoft.com > > Address 1: 104.88.47.193 a104-88-47-193.deploy.static.akamaitechnologies.com A reverse DNS lookup was performed > > Address 2: 2001:418:143c:19e::356e > > Address 3: 2001:418:143c:1a9::356e > > > > real0m40.071s > > user0m0.000s > > sys 0m0.001s > > > > What times do you get if you do a nslookup on www.microsoft.com? > > | $ time nslookup www.microsoft.com 172.24.0.7 > | Server: 172.24.0.7 > | Address:172.24.0.7#53 No sign that nslookup did a reverse lookup. > | Non-authoritative answer: > | www.microsoft.com canonical name = www.microsoft.com-c-3.edgekey.net. > | www.microsoft.com-c-3.edgekey.net canonical name = > www.microsoft.com-c-3.edgekey.net.globalredir.akadns.net. > | www.microsoft.com-c-3.edgekey.net.globalredir.akadns.netcanonical name > = e13678.dspb.akamaiedge.net. > | Name: e13678.dspb.akamaiedge.net > | Address: 104.73.152.80 No sign that nslookup did a reverse lookup. > | real0m0,261s > | user0m0,006s > | sys 0m0,006s Considered "fast" > | $ time host www.microsoft.com 172.24.0.7 > | Using domain server: > | Name: 172.24.0.7 > | Address: 172.24.0.7#53 > | Aliases: > | > | www.microsoft.com is an alias for www.microsoft.com-c-3.edgekey.net. > | www.microsoft.com-c-3.edgekey.net is an alias for > www.microsoft.com-c-3.edgekey.net.globalredir.akadns.net. > | www.microsoft.com-c-3.edgekey.net.globalredir.akadns.net is an alias for > e13678.dspb.akamaiedge.net. > | e13678.dspb.akamaiedge.net has address 104.73.152.80 > | e13678.dspb.akamaiedge.net has IPv6 address 2a02:26f0:f4:196::356e > | e13678.dspb.akamaiedge.net has IPv6 address 2a02:26f0:f4:19f::356e > | > | real0m0,096s > | user0m0,008s > | sys 0m0,004s faster as nslookup. Groeten Geert Stappers -- Leven en laten leven ___
Re: [Dnsmasq-discuss] Long nslookup times
On Wed, Feb 21, 2018 at 05:03:34PM +, Donald Muller wrote: > boun...@lists.thekelleys.org.uk] On Behalf Of Geert Stappers > Sent: Wednesday, January 31, 2018 5:33 PM > > On Wed, Jan 31, 2018 at 04:44:03PM +, Donald Muller wrote: > > > boun...@lists.thekelleys.org.uk] On Behalf Of Geert Stappers > > > Sent: Wednesday, January 31, 2018 4:56 AM > > > > On Wed, Jan 31, 2018 at 10:22:53AM +0100, Geert Stappers wrote: > > > > > On Tue, Jan 30, 2018 at 05:08:05PM +, Donald Muller wrote: > > > > > > > > > > > > Using Microsoft DNS server > > > > > > [~] # time nslookup www.microsoft.com 192.168.22.200 Address 1: > > > > > > 192.168.22.200 djmfs1.djmuller.com > > > > > > > > > > Programm nslookup did a reverse lookup on used DNS address and got > > > > > back a FQDN > > > > > > > > > > > Using dnsmasq > > > > > > [~] # time nslookup www.microsoft.com 192.168.22.220 Address 1: > > > > > > 192.168.22.220 DJMFS2 > > > > > > > > > > Non Fully Qualified Domain Name for the used DNS address > > > > > > > > > > > > > > > > > real0m40.057s > > > > > > > > > > Wow, a full forty seconds ... > > > > > > > > > I'm not convinced that the culprit is in dnsmasq. > > Please continue to find proof ... > > > > > > > > What additional information do you need? > > > > > The connection between the r2012 server and the router. > > > > > The connection between the dnsmasq and the router. > > > > And > > > > the connection between the nslookup client and the r2012 server the > > > > connection between the nslookup client and the dnsmasq server > > > All devices, including the router, are connected at 1GB to a switch. > > > > The testclient what does it have in /etc/resolv.conf while testing? > > Other tools for `nslookup`, such as `dig` and `host`, what timing results > > have > > those? > > The QNAP NAS with dnsmasq, how much traffic must it handle? > > The test client has the following in reslov.conf > > [~] # cat /etc/resolv.conf > nameserver 192.168.22.220 > nameserver 192.168.22.242 > > host shows the following: > > [~] # time host www.microsoft.com 192.168.22.220 > Using domain server: > Name: 192.168.22.220 > Address: 192.168.22.220#53 > Aliases: > > www.microsoft.com is an alias for www.microsoft.com-c-3.edgekey.net. > www.microsoft.com-c-3.edgekey.net is an alias for > www.microsoft.com-c-3.edgekey.net.globalredir.akadns.net. > www.microsoft.com-c-3.edgekey.net.globalredir.akadns.net is an alias for > e13678.dspb.akamaiedge.net. > e13678.dspb.akamaiedge.net has address 104.88.47.193 > e13678.dspb.akamaiedge.net has IPv6 address 2001:418:143c:19e::356e > e13678.dspb.akamaiedge.net has IPv6 address 2001:418:143c:1a9::356e > > real0m0.050s > user0m0.001s > sys 0m0.001s > > dig is not installed. > > The QNAP NAS is not handling much traffic. If is a home file server with > minimal traffic. > > I also set up dnsmasq on a second NAS with just DNS running, no DHCP. This > NAS is used for backups so normally has no traffic. I get the same long times > > [~] # time nslookup www.microsoft.com 192.168.22.242 > Server:192.168.22.242 > Address 1: 192.168.22.242 djmfs3.djmuller.com > > Name: www.microsoft.com > Address 1: 104.88.47.193 a104-88-47-193.deploy.static.akamaitechnologies.com > Address 2: 2001:418:143c:19e::356e > Address 3: 2001:418:143c:1a9::356e > > real0m40.071s > user0m0.000s > sys 0m0.001s > > What times do you get if you do a nslookup on www.microsoft.com? | $ time nslookup www.microsoft.com 172.24.0.7 | Server: 172.24.0.7 | Address: 172.24.0.7#53 | | Non-authoritative answer: | www.microsoft.com canonical name = www.microsoft.com-c-3.edgekey.net. | www.microsoft.com-c-3.edgekey.net canonical name = www.microsoft.com-c-3.edgekey.net.globalredir.akadns.net. | www.microsoft.com-c-3.edgekey.net.globalredir.akadns.net canonical name = e13678.dspb.akamaiedge.net. | Name: e13678.dspb.akamaiedge.net | Address: 104.73.152.80 | | | real 0m0,261s | user 0m0,006s | sys 0m0,006s | $ time host www.microsoft.com 172.24.0.7 | Using domain server: | Name: 172.24.0.7 | Address: 172.24.0.7#53 | Aliases: | | www.microsoft.com is an alias for www.microsoft.com-c-3.edgekey.net. | www.microsoft.com-c-3.edgekey.net is an alias for www.microsoft.com-c-3.edgekey.net.globalredir.akadns.net. | www.microsoft.com-c-3.edgekey.net.globalredir.akadns.net is an alias for e13678.dspb.akamaiedge.net. | e13678.dspb.akamaiedge.net has address 104.73.152.80 | e13678.dspb.akamaiedge.net has IPv6 address 2a02:26f0:f4:196::356e | e13678.dspb.akamaiedge.net has IPv6 address 2a02:26f0:f4:19f::356e | | real 0m0,096s | user 0m0,008s | sys 0m0,004s ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] Long nslookup times
Sorry for the delayed response. Life got in the way 😊 > -Original Message- > From: Dnsmasq-discuss [mailto:dnsmasq-discuss- > boun...@lists.thekelleys.org.uk] On Behalf Of Geert Stappers > Sent: Wednesday, January 31, 2018 5:33 PM > To: dnsmasq-discuss@lists.thekelleys.org.uk > Subject: Re: [Dnsmasq-discuss] Long nslookup times > > On Wed, Jan 31, 2018 at 04:44:03PM +, Donald Muller wrote: > > boun...@lists.thekelleys.org.uk] On Behalf Of Geert Stappers > > Sent: Wednesday, January 31, 2018 4:56 AM > > > On Wed, Jan 31, 2018 at 10:22:53AM +0100, Geert Stappers wrote: > > > > On Tue, Jan 30, 2018 at 05:08:05PM +, Donald Muller wrote: > > > > > > > > > > Using Microsoft DNS server > > > > > > > > > > [~] # time nslookup www.microsoft.com 192.168.22.200 Address 1: > > > > > 192.168.22.200 djmfs1.djmuller.com > > > > > > > > Programm nslookup did a reverse lookup on used DNS address and got > > > > back a FQDN > > > > > > > > > Address 1: 172.229.210.230 > > > > > a172-229-210-230.deploy.static.akamaitechnologies.com > > > > > > > > > > real0m0.103s > > > > > > > > > > Using dnsmasq > > > > > > > > > > [~] # time nslookup www.microsoft.com 192.168.22.220 Address 1: > > > > > 192.168.22.220 DJMFS2 > > > > > > > > Non Fully Qualified Domain Name for the used DNS address > > > > > > > > > Address 1: 172.229.210.230 > > > > > a172-229-210-230.deploy.static.akamaitechnologies.com > > > > > > > > > > real0m40.057s > > > > > > > > Wow, a full forty seconds ... > > > > > > > > > As you can see dnsmasq took a lot longer. > > > > > > > > > Both DNS servers are set up to > > > > > forward requests to my router (192.168.22.252) which then > > > > > forwards them on the my ISP DNS servers. The router is NOT running > a DNS server. > > > > > > > > So the "forward" is about forwarding plain IP packets. > > > > Initially I did read the "forward" as "forwarding a DNS request" > > > > > > > > > > > > > Some queries run faster on the NAS. Others, like > > > > > www.micorsoft.com run slower. Here is my dnsmasq setup. > > > > > > > > > > Main dnsmasq config file > > > > > > Is there a setting that needs to be changed/added/removed? > > I'm not convinced that the culprit is in dnsmasq. > Please continue to find proof ... > > > > > > What additional information do you need? > > > > > > > > > > > > > The connection between the r2012 server and the router. > > > > The connection between the dnsmasq and the router. > > > > > > And > > > the connection between the nslookup client and the r2012 server the > > > connection between the nslookup client and the dnsmasq server > > > > > > > All devices, including the router, are connected at 1GB to a switch. > > The testclient what does it have in /etc/resolv.conf while testing? > Other tools for `nslookup`, such as `dig` and `host`, what timing results have > those? > The QNAP NAS with dnsmasq, how much traffic must it handle? The test client has the following in reslov.conf [~] # cat /etc/resolv.conf nameserver 192.168.22.220 nameserver 192.168.22.242 host shows the following: [~] # time host www.microsoft.com 192.168.22.220 Using domain server: Name: 192.168.22.220 Address: 192.168.22.220#53 Aliases: www.microsoft.com is an alias for www.microsoft.com-c-3.edgekey.net. www.microsoft.com-c-3.edgekey.net is an alias for www.microsoft.com-c-3.edgekey.net.globalredir.akadns.net. www.microsoft.com-c-3.edgekey.net.globalredir.akadns.net is an alias for e13678.dspb.akamaiedge.net. e13678.dspb.akamaiedge.net has address 104.88.47.193 e13678.dspb.akamaiedge.net has IPv6 address 2001:418:143c:19e::356e e13678.dspb.akamaiedge.net has IPv6 address 2001:418:143c:1a9::356e real0m0.050s user0m0.001s sys 0m0.001s dig is not installed. The QNAP NAS is not handling much traffic. If is a home file server with minimal traffic. I also set up dnsmasq on a second NAS with just DNS running, no DHCP. This NAS is used for backups so normally has no traffic. I get the same long times [~] # time nslookup www.microsoft.com 192.168.22.242 Server:192.168.22.242 Address 1: 192.168.22.242 djmfs3.djmuller.com Name: www.microsoft.com Address 1: 104.88.47.193 a104-88-47-193.deploy.static.akamaitechnologies.com Address 2: 2001:418:143c:19e::356e Address 3: 2001:418:143c:1a9::356e real0m40.071s user0m0.000s sys 0m0.001s What times do you get if you do a nslookup on www.microsoft.com? > > > Groeten > Geert Stappers > -- > 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 mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] Long nslookup times
On Wed, Jan 31, 2018 at 04:44:03PM +, Donald Muller wrote: > boun...@lists.thekelleys.org.uk] On Behalf Of Geert Stappers > Sent: Wednesday, January 31, 2018 4:56 AM > > On Wed, Jan 31, 2018 at 10:22:53AM +0100, Geert Stappers wrote: > > > On Tue, Jan 30, 2018 at 05:08:05PM +, Donald Muller wrote: > > > > > > > > Using Microsoft DNS server > > > > > > > > [~] # time nslookup www.microsoft.com 192.168.22.200 Address 1: > > > > 192.168.22.200 djmfs1.djmuller.com > > > > > > Programm nslookup did a reverse lookup on used DNS address and got > > > back a FQDN > > > > > > > Address 1: 172.229.210.230 > > > > a172-229-210-230.deploy.static.akamaitechnologies.com > > > > > > > > real0m0.103s > > > > > > > > Using dnsmasq > > > > > > > > [~] # time nslookup www.microsoft.com 192.168.22.220 Address 1: > > > > 192.168.22.220 DJMFS2 > > > > > > Non Fully Qualified Domain Name for the used DNS address > > > > > > > Address 1: 172.229.210.230 > > > > a172-229-210-230.deploy.static.akamaitechnologies.com > > > > > > > > real0m40.057s > > > > > > Wow, a full forty seconds ... > > > > > > > As you can see dnsmasq took a lot longer. > > > > > > > Both DNS servers are set up to > > > > forward requests to my router (192.168.22.252) which then forwards > > > > them on the my ISP DNS servers. The router is NOT running a DNS server. > > > > > > So the "forward" is about forwarding plain IP packets. > > > Initially I did read the "forward" as "forwarding a DNS request" > > > > > > > > > > Some queries run faster on the NAS. Others, like www.micorsoft.com > > > > run slower. Here is my dnsmasq setup. > > > > > > > > Main dnsmasq config file > > > > Is there a setting that needs to be changed/added/removed? I'm not convinced that the culprit is in dnsmasq. Please continue to find proof ... > > > > What additional information do you need? > > > > > > > > > > The connection between the r2012 server and the router. > > > The connection between the dnsmasq and the router. > > > > And > > the connection between the nslookup client and the r2012 server the > > connection between the nslookup client and the dnsmasq server > > > > All devices, including the router, are connected at 1GB to a switch. The testclient what does it have in /etc/resolv.conf while testing? Other tools for `nslookup`, such as `dig` and `host`, what timing results have those? The QNAP NAS with dnsmasq, how much traffic must it handle? Groeten Geert Stappers -- Leven en laten leven ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] Long nslookup times
> -Original Message- > From: Dnsmasq-discuss [mailto:dnsmasq-discuss- > boun...@lists.thekelleys.org.uk] On Behalf Of Geert Stappers > Sent: Wednesday, January 31, 2018 4:56 AM > To: dnsmasq-discuss@lists.thekelleys.org.uk > Subject: Re: [Dnsmasq-discuss] Long nslookup times > > On Wed, Jan 31, 2018 at 10:22:53AM +0100, Geert Stappers wrote: > > On Tue, Jan 30, 2018 at 05:08:05PM +, Donald Muller wrote: > > > > > > Using Microsoft DNS server > > > > > > [~] # time nslookup www.microsoft.com 192.168.22.200 Address 1: > > > 192.168.22.200 djmfs1.djmuller.com > > > > Programm nslookup did a reverse lookup on used DNS address and got > > back a FQDN > > > > > Address 1: 172.229.210.230 > > > a172-229-210-230.deploy.static.akamaitechnologies.com > > > > > > real0m0.103s > > > > > > Using dnsmasq > > > > > > [~] # time nslookup www.microsoft.com 192.168.22.220 Address 1: > > > 192.168.22.220 DJMFS2 > > > > Non Fully Qualified Domain Name for the used DNS address > > > > > Address 1: 172.229.210.230 > > > a172-229-210-230.deploy.static.akamaitechnologies.com > > > > > > real0m40.057s > > > > Wow, a full forty seconds ... > > > > > As you can see dnsmasq took a lot longer. > > > > > Both DNS servers are set up to > > > forward requests to my router (192.168.22.252) which then forwards > > > them on the my ISP DNS servers. The router is NOT running a DNS server. > > > > So the "forward" is about forwarding plain IP packets. > > Initially I did read the "forward" as "forwarding a DNS request" > > > > > > > Some queries run faster on the NAS. Others, like www.micorsoft.com > > > run slower. Here is my dnsmasq setup. > > > > > > Main dnsmasq config file > > > > > > user=x > > > group=yyy > > > log- > facility=/share/CACHEDEV1_DATA/UserData/Logs/DNSMasq/dnsmasq.log > > > log-async=25 > > > bind-dynamic > > > conf- > file=/share/CACHEDEV1_DATA/UserData/Configs/DNSMasq/dnsmasq-dns > > > .conf # DNS configuration information > > > conf- > file=/share/CACHEDEV1_DATA/UserData/Configs/DNSMasq/dnsmasq-dhc > > > p.conf # DHCP configuration information > > > > > > dnsmasq-dns.conf file > > > > > > domain-needed > > > domain=djmuller.com > > > no-hosts > > > addn- > hosts=/share/CACHEDEV1_DATA/UserData/Configs/DNSMasq/dnsmasq-ho > > > sts.conf > > > expand-hosts > > > #log-queries > > > local-service > > > bogus-priv > > > filterwin2k > > > resolv- > file=/share/CACHEDEV1_DATA/UserData/Configs/DNSMasq/dnsmasq-r > > > esolv.conf > > > stop-dns-rebind > > > rebind-localhost-ok > > > no-poll > > > clear-on-reload > > > domain-needed > > > mx-host=djmuller.com,djmuller.com,50 > > > mx-target=mail.djmuller.com > > > cache-size=1000 > > > conf- > file=/share/CACHEDEV1_DATA/UserData/Configs/DNSMasq/dnsmasq-ads > > > ervers.conf # List of servers that will return no-domain > > > rebind-domain-ok=/plex.direct/ > > > > > > Is there a setting that needs to be changed/added/removed? > > > What additional information do you need? > > > > > > > The connection between the r2012 server and the router. > > The connection between the dnsmasq and the router. > > And > the connection between the nslookup client and the r2012 server the > connection between the nslookup client and the dnsmasq server > All devices, including the router, are connected at 1GB to a switch. > Groeten > Geert Stappers > Who thinks this mail thread is not about a dnsmasq issue > -- > 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 mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] Long nslookup times
On Wed, Jan 31, 2018 at 10:22:53AM +0100, Geert Stappers wrote: > On Tue, Jan 30, 2018 at 05:08:05PM +, Donald Muller wrote: > > > > Using Microsoft DNS server > > > > [~] # time nslookup www.microsoft.com 192.168.22.200 > > Address 1: 192.168.22.200 djmfs1.djmuller.com > > Programm nslookup did a reverse lookup on used DNS address > and got back a FQDN > > > Address 1: 172.229.210.230 > > a172-229-210-230.deploy.static.akamaitechnologies.com > > > > real0m0.103s > > > > Using dnsmasq > > > > [~] # time nslookup www.microsoft.com 192.168.22.220 > > Address 1: 192.168.22.220 DJMFS2 > > Non Fully Qualified Domain Name for the used DNS address > > > Address 1: 172.229.210.230 > > a172-229-210-230.deploy.static.akamaitechnologies.com > > > > real0m40.057s > > Wow, a full forty seconds ... > > > As you can see dnsmasq took a lot longer. > > > Both DNS servers are set up to > > forward requests to my router (192.168.22.252) which then forwards them > > on the my ISP DNS servers. The router is NOT running a DNS server. > > So the "forward" is about forwarding plain IP packets. > Initially I did read the "forward" as "forwarding a DNS request" > > > > Some queries run faster on the NAS. Others, like www.micorsoft.com run > > slower. Here is my dnsmasq setup. > > > > Main dnsmasq config file > > > > user=x > > group=yyy > > log-facility=/share/CACHEDEV1_DATA/UserData/Logs/DNSMasq/dnsmasq.log > > log-async=25 > > bind-dynamic > > conf-file=/share/CACHEDEV1_DATA/UserData/Configs/DNSMasq/dnsmasq-dns.conf > > # DNS configuration information > > conf-file=/share/CACHEDEV1_DATA/UserData/Configs/DNSMasq/dnsmasq-dhcp.conf > > # DHCP configuration information > > > > dnsmasq-dns.conf file > > > > domain-needed > > domain=djmuller.com > > no-hosts > > addn-hosts=/share/CACHEDEV1_DATA/UserData/Configs/DNSMasq/dnsmasq-hosts.conf > > expand-hosts > > #log-queries > > local-service > > bogus-priv > > filterwin2k > > resolv-file=/share/CACHEDEV1_DATA/UserData/Configs/DNSMasq/dnsmasq-resolv.conf > > stop-dns-rebind > > rebind-localhost-ok > > no-poll > > clear-on-reload > > domain-needed > > mx-host=djmuller.com,djmuller.com,50 > > mx-target=mail.djmuller.com > > cache-size=1000 > > conf-file=/share/CACHEDEV1_DATA/UserData/Configs/DNSMasq/dnsmasq-adservers.conf > > # List of servers that will return no-domain > > rebind-domain-ok=/plex.direct/ > > > > Is there a setting that needs to be changed/added/removed? > > What additional information do you need? > > > > The connection between the r2012 server and the router. > The connection between the dnsmasq and the router. And the connection between the nslookup client and the r2012 server the connection between the nslookup client and the dnsmasq server Groeten Geert Stappers Who thinks this mail thread is not about a dnsmasq issue -- Leven en laten leven ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] Long nslookup times
On Tue, Jan 30, 2018 at 05:08:05PM +, Donald Muller wrote: > > Using Microsoft DNS server > > [~] # time nslookup www.microsoft.com 192.168.22.200 > Server:192.168.22.200 > Address 1: 192.168.22.200 djmfs1.djmuller.com Programm nslookup did a reverse lookup on used DNS address and got back a FQDN > Name: www.microsoft.com > Address 1: 172.229.210.230 > a172-229-210-230.deploy.static.akamaitechnologies.com > Address 2: 2001:428:4404:18f::356e > Address 3: 2001:428:4404:192::356e > > real0m0.103s > > Using dnsmasq > > [~] # time nslookup www.microsoft.com 192.168.22.220 > Server:192.168.22.220 > Address 1: 192.168.22.220 DJMFS2 Non Fully Qualified Domain Name for the used DNS address > > Name: www.microsoft.com > Address 1: 172.229.210.230 > a172-229-210-230.deploy.static.akamaitechnologies.com > Address 2: 2001:428:4404:192::356e > Address 3: 2001:428:4404:18f::356e > > real0m40.057s Wow, a full forty seconds ... > As you can see dnsmasq took a lot longer. > Both DNS servers are set up to > forward requests to my router (192.168.22.252) which then forwards them > on the my ISP DNS servers. The router is NOT running a DNS server. So the "forward" is about forwarding plain IP packets. Initially I did read the "forward" as "forwarding a DNS request" > Some queries run faster on the NAS. Others, like www.micorsoft.com run > slower. Here is my dnsmasq setup. > > Main dnsmasq config file > > user=x > group=yyy > log-facility=/share/CACHEDEV1_DATA/UserData/Logs/DNSMasq/dnsmasq.log > log-async=25 > bind-dynamic > conf-file=/share/CACHEDEV1_DATA/UserData/Configs/DNSMasq/dnsmasq-dns.conf # > DNS configuration information > conf-file=/share/CACHEDEV1_DATA/UserData/Configs/DNSMasq/dnsmasq-dhcp.conf # > DHCP configuration information > > dnsmasq-dns.conf file > > domain-needed > domain=djmuller.com > no-hosts > addn-hosts=/share/CACHEDEV1_DATA/UserData/Configs/DNSMasq/dnsmasq-hosts.conf > expand-hosts > #log-queries > local-service > bogus-priv > filterwin2k > resolv-file=/share/CACHEDEV1_DATA/UserData/Configs/DNSMasq/dnsmasq-resolv.conf > stop-dns-rebind > rebind-localhost-ok > no-poll > clear-on-reload > domain-needed > mx-host=djmuller.com,djmuller.com,50 > mx-target=mail.djmuller.com > cache-size=1000 > conf-file=/share/CACHEDEV1_DATA/UserData/Configs/DNSMasq/dnsmasq-adservers.conf > # List of servers that will return no-domain > rebind-domain-ok=/plex.direct/ > > Is there a setting that needs to be changed/added/removed? > What additional information do you need? > The connection between the r2012 server and the router. The connection between the dnsmasq and the router. Groeten Geert Stappers -- 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] Long nslookup times
Hello all, I have Microsoft DNS and DHCP running on a Windows 2012 R2 server. The processor is a 4 core 4 thread i5-4440 running at 3.1GHz with 16GB of memory. I am in the process of retiring this server and moving everything over to a QNAP NAS which runs Linux. The NAS is running a 4 core 8 thread i7-7700 running at 3.6GHz with 40GB of memory. The Linux NAS is faster and has more threads and memory. I have installed dnsmasq on the NAS and DNS and DHCP are working. However during testing I ran into a strange issue. Running an nslookup on the NAS using the DNS on the NAS takes a lot longer than it does using the DNS running on the 2012 server. Using Microsoft DNS server [~] # time nslookup www.microsoft.com 192.168.22.200 Server:192.168.22.200 Address 1: 192.168.22.200 djmfs1.djmuller.com Name: www.microsoft.com Address 1: 172.229.210.230 a172-229-210-230.deploy.static.akamaitechnologies.com Address 2: 2001:428:4404:18f::356e Address 3: 2001:428:4404:192::356e real0m0.103s user0m0.001s sys 0m0.000s Using dnsmasq [~] # time nslookup www.microsoft.com 192.168.22.220 Server:192.168.22.220 Address 1: 192.168.22.220 DJMFS2 Name: www.microsoft.com Address 1: 172.229.210.230 a172-229-210-230.deploy.static.akamaitechnologies.com Address 2: 2001:428:4404:192::356e Address 3: 2001:428:4404:18f::356e real0m40.057s user0m0.000s sys 0m0.001s As you can see dnsmasq took a lot longer. Both DNS servers are set up to forward requests to my router (192.168.22.252) which then forwards them on the my ISP DNS servers. The router is NOT running a DNS server. Some queries run faster on the NAS. Others, like www.micorsoft.com run slower. Here is my dnsmasq setup. Main dnsmasq config file user=x group=yyy log-facility=/share/CACHEDEV1_DATA/UserData/Logs/DNSMasq/dnsmasq.log log-async=25 bind-dynamic conf-file=/share/CACHEDEV1_DATA/UserData/Configs/DNSMasq/dnsmasq-dns.conf # DNS configuration information conf-file=/share/CACHEDEV1_DATA/UserData/Configs/DNSMasq/dnsmasq-dhcp.conf # DHCP configuration information dnsmasq-dns.conf file domain-needed domain=djmuller.com no-hosts addn-hosts=/share/CACHEDEV1_DATA/UserData/Configs/DNSMasq/dnsmasq-hosts.conf expand-hosts #log-queries local-service bogus-priv filterwin2k resolv-file=/share/CACHEDEV1_DATA/UserData/Configs/DNSMasq/dnsmasq-resolv.conf stop-dns-rebind rebind-localhost-ok no-poll clear-on-reload domain-needed mx-host=djmuller.com,djmuller.com,50 mx-target=mail.djmuller.com cache-size=1000 conf-file=/share/CACHEDEV1_DATA/UserData/Configs/DNSMasq/dnsmasq-adservers.conf # List of servers that will return no-domain rebind-domain-ok=/plex.direct/ Is there a setting that needs to be changed/added/removed? What additional information do you need? Thanks Don ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
