I've dug into dnsmasq manual, and I believe thant '--dhcp-authoritative' should not be used in the neutron dhcp agent.
-K, --dhcp-authoritative Should be set when dnsmasq is definitely the only DHCP server on
a network. For DHCPv4, it changes the behaviour from strict RFC compliance so that DHCP requests on unknown leases from unknown
hosts are not ignored. This allows new hosts to get a lease without a tedious timeout under all circumstances. It also allows dnsmasq to rebuild its lease database without each client needing to reacquire a lease, if the database is lost. For DHCPv6 it sets the priority in replies to 255 (the maximum) instead of 0 (the minimum).
As we understand, if there is more than one dnsmasq on the network it will violate --dhcp-authoritative expectations.
I've dug into dnsmasq manual, and I believe thant '--dhcp- authoritative' should not be used in the neutron dhcp agent.
-K, --dhcp- authoritative
Should be set when dnsmasq is definitely the only DHCP server on
compliance so that DHCP requests on unknown leases from unknown
without a tedious timeout under all circumstances. It also
allows dnsmasq to rebuild its lease database without each client
needing to reacquire a lease, if the database is lost. For
DHCPv6 it sets the priority in replies to 255 (the maximum)
instead of 0 (the minimum).
a network. For DHCPv4, it changes the behaviour from strict RFC
hosts are not ignored. This allows new hosts to get a lease
As we understand, if there is more than one dnsmasq on the network it will violate --dhcp- authoritative expectations.