> -----Original Message-----
> From: Dnsmasq-discuss <dnsmasq-discuss-boun...@lists.thekelleys.org.uk>
> On Behalf Of Donald Muller
> Sent: Wednesday, March 7, 2018 12:23 PM
> To: email@example.com
> Subject: Re: [Dnsmasq-discuss] lame response
> > -----Original Message-----
> > From: Dnsmasq-discuss
> > <dnsmasq-discuss-boun...@lists.thekelleys.org.uk>
> > On Behalf Of Yeah
> > Sent: Monday, March 5, 2018 12:01 PM
> > To: firstname.lastname@example.org
> > Subject: Re: [Dnsmasq-discuss] lame response
> > On Fri, Mar 02, 2018 at 05:36:03PM +0000, Donald Muller wrote:
> > > 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
> > > using the Microsoft DNS takes less than a second.
> > Nslookup ---> Name Server ---x--> Next Name Server.
> > Move to x and do testing/checking/measuring there.
> > Find out why Next Name Server is so lame in responding when Name
> > Server is dnsmasq.
> > Or find out what Name Server on MS Window 2012 is caching/lying/making
> > up.
> > See also http://www.catb.org/~esr/faqs/smart-questions.html
> Your suggestion prompted me dig deeper. I tried what you suggested and on
> checking the next name server there was no 40 second lag which points me
> back to dnsmasq. I tried to use debug on the nslookup that comes with the
> NAS but it is crippled. The only options you can use as name and server. So I
> switched to using nslookup on Win10. I put it into debug and D2 mode and
> executed a lookup using www.microsoft.com against dnsmasq. I have
> attached the debug info. As you can see a request for an (A) record was sent
> using www.microsoft.com.djmuller.com. This request to dnsmasq timed out.
> After the timeout a second request was sent for an (AAAA) record. This also
> timed out. Further requests were sent without .djmuller.com and received
> replies. When the same was executed against a Microsoft DNS server the
> same series of requests were made. However instead of the MS DNS not
> replying on the queries that had .djmuller.com on them it responded with
> NXDOMAIN. Debug file attached.
> So I think I have run into two issues. The first is nslookup on the NAS which
> a busybox version. I think the retries are set high which is causing the 40
> second timing. Since it won't accept any options there is nothing I can do
> it. So as far as I am concerned the 40 second issue is closed. The second is
> that on certain queries dnsmasq is not responding. Below is my DNS config
> for dnsmasq. Is there an option I have set or one that I don't have set that
> causing this behavior?
> adservers.conf # List of servers that will return
Did more testing and when I change the nameservers from my router (which should
be doing pass through only) to my ISP DNS servers dnsmasq no longer timed out.
So it looks like there are some things that the router doesn't like and doesn't
As far as I am concerned this issue is solved.
Dnsmasq-discuss mailing list