Active Directory on W2k3 - DNS? help
Posted on 2005-03-01
Hi all - I have been tossed into a situation where we have a single domain controller (W2k3) that was installed and configured without DNS. The short of it is, this site has been using hosts files since they were a 10 user office and for whatever reason continued to use them. Now that we have a temporary (and yes, this will all be gone in about 4-6 weeks) solution in place, I've some concerns on the way it was configured.
I 'thought' DNS was a mandatory process when configuring AD - apparently not, as the consultant that set it up got around it.
So, I'm toying with the idea of setting up both DHCP & DNS on this server (yes, they were also using and still are, static IPs - 300+ clients). However, DNS in an AD environment is something I haven't really spent much time with.
From your expert experiences, can I get some opinions/advice on setting this up?
A) Is it worth it, since we'll be moving to a stable environment beginning next week, with potentially 1/3 of the office and continuing for 3-6 weeks after (depending on each wave's success)
B) How hard would it be to do so? DNS has always been a weak point of mine and I'm concerned that I might screw something up! :)
C) Other than touching all 300+ systems again (and this includes some VPN users) - how can we easily/automate the process of switching them over to dynamic IP?
They currently use their provider's DNS servers for internet access. They have several in-house servers right now. I've removed all client entries from the hosts files via a login script - but is that enough?
100 points per bullet above. If I decide to move forward, I'll open a new thread on actually installing it... Thanx.