"Yuri NLD" <(E-Mail Removed)> wrote in message
news:3A2E7A08-D4E6-409E-ADE0-(E-Mail Removed)...
> Here an explanation of my requirement (it's a proactive solution):
> Imagine. 100 servers in your network. All configured with a static
> address.
> After some time the DNS server setting must be changed. Then you have to
> enter manually on all the servers the new DNS server setting. With a
> reservation is the scope centrally managed (one change for all servers).
> No
> chance for type errors, and so on.
>
> I know, as you explained, that the client send the broadcast. I was hoping
> for an out-of-the-box solution that the server triggers the client to
> perform
> a broadcast or something like that.
The problem is that it makes everything dependent on the DHCP server being
"alive and well" and the DHCP Server becomes the most important server on
the whole network. It never should be that way and wasn't intended for
that.
For DNS you can make sure that there is always a DNS Server at the same IP#.
Make sure that DNS will forward to others if it needs to. Besides that, DNS
Servers should not be changing all the time,...if they are then that itself
is a big problem that needs to be addressed so that they are not changing
all the time. So I disagree that "...after some time the DNS server setting
must be changed...". They should not be changed,..hardly ever. If one is
replaced give the new one the same IP#.
Besides all that,...now-a-days most DNS machines on a LAN are also Domain
Controllers,...and those should not be changing all the time.
--
Phillip Windell
www.wandtv.com
The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------