On Mon, 23 Nov 2015 15:44:42 -0800
Dave Warren <da...@hireahit.com> wrote:

> > Delete all leases from Status -> DHCP leases, restart dhcp service
> > and retry ...  
> That's not necessary and would be incorrect behaviour if it were 
> happening. I just confirmed here with my pfSense installation, new 
> options are applied without removing the old lease in all expected 
> cases, including the Domain Name field.

Thanks for confirming.

> I tested via a Domain Name change against an automatic renewal and 
> manual renewal, as well as a "release/renew" cycle; in all cases the 
> client was aware of the new settings immediately after the DHCP 
> operation completed.
> Now admittedly some broken clients won't reflect all changes 
> immediately; some of our VoIP phones will update DNS servers as soon
> as they renew, but won't update timezone information until the next
> reboot, but this is a client deficiency and nothing you do in pfSense
> (including removing the old lease) will make a difference, and it
> only causes issues on specific hardware, but if you capture and
> analyze the packets, you'll see correct data was sent by the DHCP
> server.

Thanks for the thorough answer. It seems it's not pfSense that is at
fault, but the client itself. I'll fire up wireshark and check
what's being transmitted to confirm.

pfSense mailing list
Support the project with Gold! https://pfsense.org/gold

Reply via email to