[Dnsmasq-discuss] no leases left

Hi, I very often get this message and clients cannot connect anymore because they don't get an IP address offered. Below is the log for one request Sep 26 18:40:30 dns dnsmasq-dhcp[37159]: 1029998759 available DHCP range: 192.168.0.200 -- 192.168.0.254 Sep 26 18:40:30 dns dnsmasq-dhcp[37159]:

Re: [Dnsmasq-discuss] How to let dnsmasq using multiple upstream dns servers with non-standard ports.

You can't put non-standard ports in a resolv-file, the format of those files does not include ports. It is possible to put a non-standard port in dnsmasq configuration files using server=server1#port1 So simply make your file look like server=server1#port1 server=server2#port2

Re: [Dnsmasq-discuss] strict-order still considered broken?

To be honest, I don't know. I've never tested. the Python behavour seems to me to be strange: the original socket must still be open at timeout, to receive the reply which never comes, so why not re-use it? Of course, unless using strict-order, there's no practical difference between sending two

Re: [Dnsmasq-discuss] TTL for "temporary" NXDOMAIN

The short answer is that there's no way to make dnsmasq do that. It's a pretty crazy way for a DNS server to behave. The question is, why DNS lookups to you application are failing when it restarts? DNS queries have timeouts and retries, so it should just wait for it to come back. I guess we need

Re: [Dnsmasq-discuss] no leases left

Dnsmasq has a global limit on the number of leases in use at any time, and it's that limit you're hitting, not running out of addresses. The default is 1000 leases, you can increase it by putting dhcp-lease-max=2000 ,or whatever, in the config file. Cheers, Simon. On 26/09/15 17:50, Ben

Re: [Dnsmasq-discuss] How to let dnsmasq using multiple upstream dns servers with non-standard ports.

2015-09-27 4:53 GMT+08:00 Simon Kelley : > You can't put non-standard ports in a resolv-file, the format of those > files does not include ports. > > It is possible to put a non-standard port in dnsmasq configuration files > using > > server=server1#port1 > > So simply