Yes, your new Domain Controller server needs to be configured with a static
IP. You should turn off the DHCP service in the router and let your new
Domain Controller handle DHCP for your clients.
So... the ipconfig of your workstations (and server dns client) will look
like this...
IP: 192.168.0.5 (or equiv dhcp assigned address - but server will be static)
Default Gateway: 192.168.0.1 (or equiv for the IP of your router)
DHCP Server: 192.168.0.2 (or equiv static IP of your new Domain Controller
Server running DHCP)
Configure your new server's DHCP service to also hand out the DNS server IP.
This IP will be the IP of your new Domain Controller running DNS.
You will configure your new Domain Controller DNS service to forward request
outside of your domain to the DNS servers provided by your ISP, or your
router's IP.
-Frank
"Joe Befumo" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I'm about to help a small radio station transition from a workgroup to a
> domain. They are currently using a Linksys switch that offers DHCP
> services. My question is whether the domain server can use this existing
> DHCP source, or should I set it up with a fixed IP & exclude that address
> from the Linksys's DHCP list? Thanks.
>
> Joe
> http://www.befumo.com
>
>