DNS needs static IP ?

  • Thread starter Thread starter Polaris
  • Start date Start date
P

Polaris

Hi:

I'm setting up a Windows Server 2003 as AD and DNS server, during seting up,
it recommends that the DNS server use a static IP. Could someone tell me why
?

Thanks In Advance !

Polaris
 
DNS is the directory for your system names. You need to be able to find the
DNS servers from anywhere by both name and address and the only way to
guarantee this is to statically assign IP addresses to your DNS servers.
Other services that should be statically assigned are your DHCP and WINS
servers. I run the DNS/WINS service pairs on all my name servers and have
each DNS server resolve machine level names to the local WINS server. This
way NetBIOS and IP based programs get the same addresses back from DNS and
WINS.

Mike Ober.
 
Thanks, that makes sense. I read from online that some DNS providers allow
DHCP for DNS server, may be they are able to do some kind of dynamic update
in case DNS server IP changed...
 
You can feed DHCP clients the DNS server addresses, but I haven't heard of a
DHCP server that will dynamically update the DNS server addresses. Even if
you could, you would quicly run into a situation where the DHCP supplied DNS
server addresses changes but the clients won't see the change until they
renew their leases, which on my network can be up to a month away. In any
case, the Windows DHCP server doesn't do this.

Mike Ober.
 
In principle, *all* Servers and network devices should be statically assign
(not even DHCP Reserved). Your network infrastructure should never be
dependent on a DHCP Server. DHCP should be only for the workstations of the
users.
 
Back
Top