Two possible reasons: 1) resource exhaustion - the limit on the number of "in-flight" queries has been reached. 2) Network errors sending the query upstream. As a start of debugging, I'd try without the @eth0 interface specifier.
Simon. On 22/07/2021 18:21, sunil rathod wrote: > Hi All, > Any thoughts why dnsmasq is replying with REFUSE response without > forwarding the query to upstream server? Nslookup always fails with > refuse response from the external client. I have the upstream server > configured on conf file as > server=8.8.8.8@eth0 > Regards, > Sunil > > > _______________________________________________ > Dnsmasq-discuss mailing list > Dnsmasq-discuss@lists.thekelleys.org.uk > https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss > _______________________________________________ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
