"tmosely" <todd[ at ]brazosvos.com> wrote in message
news:9B583941-5C2F-4F3C-854E-8765BA34C64A[ at ]microsoft.com...
[Quoted Text] >I am currently adding new workstations to our network and have been using a
> workgroup. When trying to join the domain I get a DNS error stating that
> it
> cannot resolve the domain name. I am not using the DNS services on the
> server
> I am using the ISP's DNS. Unsure as to how to resolve the issue. Help
Since you are going from the Workgroup to a Domain you are going to have to
throw out a *lot* of the thinking and the methodologies you currently
use,...and DNS is a *big* one.
1. You can't use the ISP's DNS any longer
2. Every single last host on the LAN *must* use the AD/DNS on the Domain
Controller. Even the Domain Controller uses only itself.
3. The AD/DNS machine (the Domain Controller) must be allowed by the
Firewall to make outbound DNS queries anonymously. With most
"home-user-NAT-boxes" [commonly and incorrectly called "routers"] this will
be already true since they do not typically out-of-the-box filter outgoing
traffic.
4. Within the configuration of the DNS Services on the Domain Controller you
have 2 choices:
a. Add the ISP's DNS to the Forwarders List
OR
b. Skip the Forwarder, and let the Service default to using Root
Hints
Most people use the Forwarder method.
Now,...DHCP...
Turn off the DHCP services completely on the "home-user-NAT-boxes" if that
is what you are doing. You will never us that again. You need to use an
Active Directory Authorized DHCP Service.
Install the DHCP Service on the Domain Controller. It is common practice to
run DNS, DHCP, and WINS (but *nothing* else) on the Domain Controller.
Create and configure the correct DHCP Scope and "authorize" and "activate"
it. This DHCP Service will automactally handle keeping the DNS Service
updated with the IP Config given to the DHCP Clients.
Here are some guidelines that I always propose for DHCP. These are my
own,...they are not out of a textbook.
1. Never have subnets larger than 254 hosts (/24 bit mask). Ethernet
efficiency degrades after 250-300 hosts although it is less obvious with
1000mbps -vs- 100mbps -vs- 10mbps.
2. One Scope per subnet
3. Use the full subnet IP range in the scope
4. Use Exclusions to limit the range of IP#s actually given out by the
Scope. You can have mulitple Exclusions.
5. Use Server Options instead of Scope Options for items that are global to
the whole LAN.
6. Use Scope Options for things that are only unique to that particular
Scope.
7. If you create an DHCP Reservations,...keep them to a minumum or none at
all. If there are a lot of them you might as well just statically assign
the config to the Clients and forget it.
--
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.
-----------------------------------------------------
|