Thank you Simon for your answer. The issue was not in dnsmasq. It was due
to definition of dns response length in our application.
Best regards,
Philippe
On Fri, Mar 22, 2019 at 6:00 PM Simon Kelley
wrote:
> Could you give more details on exactly how you're testing this?
> Whereever that error
On Wednesday 27 February 2019 17:07:21 Simon Kelley wrote:
> On 27/02/2019 15:06, Bogdan Harjoc wrote:
> > There are 50 calls to close() in dnsmasq-2.80, and 10 of them are
> > wrapped in retry_send().
> >
> > "man close" has this paragraph in the section "Dealing with error
> > returns from
Dear list,
I configured dnsmasq with enabled negative cache and neg-ttl 600. I
attempted to use it with a query that times out (configured fake dns servers
in the config file). When I ping a host, I have NXDOMAIN in logs. However,
every time I ping it dnsmasq asks those servers to resolve the
Dear list,
I configured dnsmasq with enabled negative cache and neg-ttl 600. I attempted to use it with a query that times out (configured fake dns servers in the config file). When I ping a host I have
NXDOMAIN in logs. However every time I ping it dnsmasq asks those servers to resolve the
