DHCP bug (dnsmasq or windows issue)

Software SW help
1

I have a static lease defined for a Win7 client in /etc/config/dhcp:

config host
    option name 'ws'
    option mac 'fc:aa:14:22:xx:yy'
    option ip '192.168.1.119'

If DNSMasq has been restarted recently, it will work as expected.
However, typically, when I boot the client, it gets a random dynamic address from the dynamic address range (netmask is 255.255.0.0, I use the 192.168.0.0/24 range for dynamics and 1.0/24 for statics):

1527554938 fc:aa:14:22:xx:yy 192.168.0.244 ws 01:fc:aa:14:22:xx:yy

ipconfig on the offending client also shows the bad address:

Physical Address. . . . . . . . . : FC-AA-14-22-XX-YY
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Lease Obtained. . . . . . . . . . : Monday, May 28, 2018 11:06:36 AM
Lease Expires . . . . . . . . . . : Wednesday, May 30, 2018 8:23:57 PM
IPv4 Address. . . . . . . . . . . : 192.168.0.244(Preferred)

DNSmasq is still able to resolve the name correctly (points to the dynamic IP when there’s an active lease for it).

Any ideas? This doesn’t appear to be happening with non-windows clients, but those are all on 24/7, so I don’t know if the client’s lease expiring without being renewed has anything to do with it.

2

iirc w10 has a feature to randomize mac addr
dont know the default setting but this maybe a cause

edit:
192.168.0.0/24 and …1.1/24 are not in the same subnet.
consider reducing the dynamic range to something like 50-150 and use 150+ for static leases.

or increase your netmask

3

The netmask is 255.255.0.0.