There's probably an existing lease for 192.168.0.121. Depending on
exactly how the client behaves, these can be difficult to get rid of.
Clearing the leases file is also more difficult than it might seem.
TL;DR If it's working now, that's fine. Ignore it.
Simon.
On 10/12/2019 03:30, isidore
Dear all
I have been trying to resolve that issue for the past 2 days.
I am using dnsmasq for dns and dhcp, and using the hosts file to statically
assigned ip to known hosts.
It doesn't work with the following error message:
"not giving name myhost.example.com to the DHCP lease of 192.168.0.12