• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

DNS Install for Active Directory

S

selgan828

Junior Member
I was curious if there were any active directory gurus out there that can help.

I have a new client that has an 2000 Server Domain Controller. Now I'm no expert about AD, but I know enough that you have to have DNS installed for it to work properly. The previous person that was managing this network did not install DNS onto the server. All the users take forever to logon to windows b/c of this.

What are the implications, if any, of installing DNS now? Will it break anything, what do I need to configure to make it work with the current AD?

Any help is appreciated
 
Originally posted by: selgan828
I was curious if there were any active directory gurus out there that can help.

I have a new client that has an 2000 Server Domain Controller. Now I'm no expert about AD, but I know enough that you have to have DNS installed for it to work properly. The previous person that was managing this network did not install DNS onto the server. All the users take forever to logon to windows b/c of this.

What are the implications, if any, of installing DNS now? Will it break anything, what do I need to configure to make it work with the current AD?

Any help is appreciated
Click to expand...

This question calls for all kinds of conjecture and guesswork. Typically your DC (for a small network) also hosts DNS. Why isn't DNS already installed, and what are you using for DNS? Your ISP's DNS servers? If so, you'll only resolve local machine by broadcast, and you'll have all kinds of issues.

By all means, set up DNS, set up DHCP to tell clients to use that DNS, and set DNS to forward requests to your ISP's DNS servers.
 
My recommendations are similar to dclive's.

I'd recommend turning off any other DHCP server on your network (hardware router, for instance) and installing a DHCP and a DNS Server on the Windows 2000 Domain Controller. You'll find that the network runs a lot smoother when all the PCs can easily locate each other. There aren't any negative consequences to adding a local DNS Server.

Make the Server's DNS Server the DNS Server for all the client PCs and for itself (this will likely happen by default when you turn on the Server's DHCP Server). Tell the Server's DNS Server to forward requests for non-local names to your ISP's DNS Server, or use Root Hints to resolve the names.
 
DNS was not installed when the server was deployed (im assuming) b/c their IT guy that deployed it didn't really know what he was doing.

I'll go ahead and install DNS and report back.

Thanks for the suggestions.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top