Hi, There have been a number of people chasing an issue in Openstack where dnsmasq was sending DHCPNAK's after it was restarted since it's being started with --leasefile-ro (https://launchpad.net/bugs/1345947).
The first solution was to create a script that could be called to re-populate the database inside dnsmasq based on the current contents of the "hosts" file that had been created (https://review.openstack.org/#/c/108272/). But then today someone else found the --dhcp-authoritative option (https://review.openstack.org/#/c/152080/) that seems to be an even easier solution. Since when Openstack is managing the DHCP service it *is* the authoritative server, this seems like the correct fix. Does anyone see any problem with this approach even when there are multiple dnsmasq processes being run (for HA), since both are under control of the same DHCP authority? I'm hoping not as this would be a much easier fix. Thoughts? Thanks, -Brian _______________________________________________ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
