I understand this is hardcoded to a limit of 1 but we use it for a small
ISP network and quite often reach this, is it possible to make it 25000 in next
release? Everyone has the choice at loading what to set it to, so I can't see
how this would cause issues. I would prefer to just
On Fri, Apr 7, 2017 at 11:27 PM, Simon Kelley wrote:
> The overriding objection to this is that it adds to the syntax and
> semantics of the resolv-file format, but dnsmasq doesn't "own" that
> format: it's actually a libc configuration file, and dnsmasq takes
FYI, changing resolv.conf format could lead libc resolver to fail, so it's
quite dangerous change.
As I understand, you want dynamic DNS servers update with additional info
(interface/src ip binding).
With no DBUS, can't it be done with --servers-file option (available since
On Mon, Apr 10, 2017 at 1:53 PM, Vladislav Grishenko
> FYI, changing resolv.conf format could lead libc resolver to fail, so it's
> quite dangerous change.
> As I understand, you want dynamic DNS servers update with additional info
> (interface/src ip
If you hit a cache limit of 1 quite often, are you sure dnsmasq is still
the best choice for that server? I think dnsmasq focuses on small home routers
and end networks. Have you considered other caching resolver, unbound for
example? I think if this limit is not enough, maybe
Just thinking out loud:
> There is only about 1000 endpoints of various types, from residential
Having worked with Unbound and dnsmasq, I would say the proverb "right
tool for the right job applies." I would guess not all 1000 endpoints
are on one subnet, maybe
I guess that is totally possible, I had just used it for a few other projects
so figured if it works why not use it :) The only things I use are setting
minimum cache ttl to 30 mins and max cache size to 10k. There is only about
1000 endpoints of various types, from residential to
I’m facing an issue on dhcp_release and dnsmasq in OpenStack and would
appreciate any help or pointers to find the root cause.
dnsmasq is receiving if_nametoindex("lo”) instead of 1939, the index for
tap2bb5e1af-d3 that was issued by dhcp_release command.
The DHCP RELEASE