Propagating changes to DNS servers to DHCP clients

[woodstockday]

I have a routed network with 8 subnets all served by a 3550 running a DHCP server.  I have 8 dhcp pools set up, one for each subnet.  Currently there are about 100 dhcp clients with leases across those subnets.   I had to change the DNS server list for each of the dhcp pools.  How do I ensure that the new DNS server info gets to all clients?   Will the clients get updated DNS info by virtue of the changes I made to the dhcp pools, or do Ineed to wait until the leases are renewed for the changes to propagate?  If so, short of having each client release/renew, is there a way to force the change?  I know that I can start/stop the dhcp server which I believe will clear all bindings which then in turn will force all clients to get a new lease.  Is there any other way to propagate the DNS change?

[lgijssel · Accepted solution]

It should change automatically when you modify the parameters. No need to stop/start dhcp for that.

As as an alternative, it will certainly be updated when the clients are rebooted.

Best is to change it after office hours, systems will be updated when the users start their PC's in the morning.

regards,

Leo

[woodstockday]

Thank you Leo.   I am relatively new to network management.  I had looked for an answer to this, but could not find one, possibly because it is well understood that the changes propagate to clients immediately?  Anyway, thanks again!

Tom