Windows Forum

Ask something
Discussion Locked

Domain Naming with Active Directory

0 helpful
5 replies

by cp409sd 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

This is my first win2k server install and I am having problems. This is the only win2000 server, or any kind of server, on my network. I receive 'netlogon' errors in the event log upon startup. From what I understand these errors stem from incorrect DNS configuration. Possibly the root of the problem is the name of my domain itself though. When I set it up, I decided to name it, say, acme.com, which is the same name as our web site, which is physically located on another network(our ISP's) I am starting to think this was a mistake. Should I have named it something like sandiego.acme.com?

If this is indeed what is wrong, I am not sure what I need to do to correct this. Do I need to create new forward and reverse lookup zones and delete the current ones? Besides the errors I receive upon startup, the system is working correctly and able to see everything.

Currently in the 'forwarders' tab of DNS settings is where I list my ISP's DNS servers(and no where else). 'Root Hints' seem to be in order from what I have seen of other people's. Under my TCP/IP properties of the LAN, the primary and secondary DNS servers, are the loopback address, and the actual IP address of this domain controler(in that order). Thanks for anything you can help me with.

5 replies

by sativocomputerservices

I had similar problems bringing up my server for the first time. The most important thing to remember is that the 2000 domain must be able to register itself with the DNS server. If it is not allowed to do so, you will have problems. Also when you did configure teh server, naming it as "acme.com" is the same name as an existing DNS zone. You are on the right track with sandiego.acme.com. Just make sure that your AD domain will not conflict with an existing DNS zone. It also helps to make sure that your DNS servers and WINS serevrs are pointing to your domain controller if it is also your WIND/DNS server. Keep in mind taht when your PC's join the domain that their DNS info will change to PCXXXX.sandiego.acme.com. Check your TCP/IP settings on your workstations if you do not want this to happen.

by cp409sd

So was it a mistake to name this domain 'acme.com'? Or do I just need to adjust my DNS settings? If it was a mistake to name my win2k domain this, how can I remedy this? Do I need to do a complete re-install? Before Active Directory came along I felt I had a good understanding of DNS, now I just feel so lost. Thanks for the help.

by sativocomputerservices

Yes.. you will have to reinstall your server. It is definitely a pain. 2000 server uses LDAP queries against DNS for name resolution in AD. When you do reload your server, name it something differentthan an existing DNS zone. (ex. sandiego.acme.com)

This discussion is closed to new replies.