DHCPv4 behavior

[kss]

I am running 22.1.8_1 presently and noticed the following:

LAN IP: 192.168.1.0/24

Old DHCP lease pool: 192.168.1.10 to 192.168.1.30
There were about 15 machines with a valid lease on this network as shown by the Services->DHCPv4->Leases menu

I moved the pool from the above to 192.168.1.60 to 192.168.1.80

Now the Services->DHCPv4->Leases list is empty, although all the issued leases are still valid and functional. I restarted the DHCP service, but the machines have not yet got their new IP assignments and do not show up.

Is this the expected behavior? Shouldn't the existing (valid) leases still be displayed even though they are no longer in the pool?

[cookiemonster]

The leases are requested, not pushed to clients. I therefore expect them to appear only when the clients have requested a new one and issued from the new pool. I haven't tested it though.
Meanwhile the old ones would have been cleared from OPN with the pool change & restart.
Could you try forcing a client to request a new ip to verify?

[axsdenied]

The leases are requested, not pushed to clients. I therefore expect them to appear only when the clients have requested a new one and issued from the new pool. I haven't tested it though.
Meanwhile the old ones would have been cleared from OPN with the pool change & restart.
Could you try forcing a client to request a new ip to verify?

This!

[kss]

I did, and it works as you said. Thanks.