Creating a domain and DNS question

Tags:
DHCP
DNS
Implementation
Microsoft Windows
Networking
Planning
Security
Hello, my company is on Netware 5.1 and we are planning to remove netware entirely and move to Microsoft Server 2003. We have two sites: One in LA and one in SLC. There is connectivity between the two and both are on separate subnets. Out goal is to put the company on a domain. Right now in SLC (main office), we have 2 Windows 2000 servers. One is running DHCP and DNS and another is running a secondary of both those services. We are getting two completely new servers for both locations to take over the Netware servers that are there now. My question is: Do I have to do anything to the DNS and DHCP configuration on the other servers? Or should I move those services to the new server which will be the domain controller? If I make the current DNS server join the domain once it's setup, should that be all I need to do?

Answer Wiki

Thanks. We'll let you know when a new response is added.

When you build the 2 new Windows 2000/03 servers it would be easier if you load DNS on the servers. This will allow you to move the DNS zone for the Windows 2000 domain into an Active Directory Integrated zone. AD integrated zones are easier to manage than traditional Primary DNS zones like the one that exists on your current DNS server.

In order do this you could:

1) Install a new server
2) Make it a secondary server for the DNS zone
3) Allow a Zone transfer to occur
4) Make the new server the primary DNS for the zone
5) Use DCPROMO to make the new server the first domain controller in the Windows Active Directory Domain
6) Build the 2nd new server (Installed DNS on the server, but make sure it points to new server 1 as the primary DNS).
7) Use DCPROMO to make the 2nd new server another domain controller

Now all systems can use New Server 1 as the primary DNS and New Server 2 as the secondary DNS. The DNS on the old WIndows 2000 server can be uninstalled if you like. Keep in mind that only YOU have all the information about the configuration of the DNS server and the DNS zones. My response assumes that the only zone on the old DNS server is the zone that represents your internal corporate infrastructure, which you will be using as the AD domain. If you have external systems pointing to the current Windows 2000 DNS server, or additional zones on the server you will need to take appropriate steps.

As for the DHCP server, you will want to join the AD domain as soon as it is built. You will then need to AUTHORIZE the DHCP server to act on systems within the domain. This is done in the DHCP MMC by right clicking on the server and clicking Authorize. If you do not perform this step, your DHCP server will not give out IP addresses.

Please keep in mind that these are general steps. There is no replacment for proper planning and testing.

If you have further questions, feel free to post them.

Discuss This Question: 5  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Natethegreat
    So if the new server2 is going to be in LA on a different subnet, it can still use the active directory on new server1? And do you need to use DCPROMO on new server1 after you setup active directory? doesn't that make it the primary domian controller after AD is installed? Other thatn that I believe you answered about everything, I really appreciate it!
    0 pointsBadges:
    report
  • PaulHinsberg
    So if the new server2 is going to be in LA on a different subnet, it can still use the active directory on new server1? If the new server2 is going to be on a different subnet, you will want to: 1) Put server2 on the same subnet as server1 (after server1 has created the Active Directory) 2) Make sure that a SUBNET and Site are defined for the IP subnet of the LA location 3) Move the server2 in Active Directory Sites and Services to the new Site for LA 4) Ship Server2 to LA and power it up. And do you need to use DCPROMO on new server1 after you setup active directory? doesn't that make it the primary domian controller after AD is installed? When you build server1 and put Windows 2000 (or 2003) on it, the DCPROMO is the next step. DCPROMO will give you the option to create a New Active Directory Domain or join and existing one. When setting up server1 you will want to create a new Active Directory domain as you do not have a pre-existing domain at this time. When you build server2 you will select the option to become an additional domain controller in an existing domain. Primary Domain controllers do not really exist in the Windows 2000 architecture. There are however, Master Opertions servers. Aside from these Flxeible Single Master Operations (FSMO - pronounced Fizz-MO) servers, all of the Windows 2000/03 Domain Controllers are peers.
    15 pointsBadges:
    report
  • Natethegreat
    Both servers are going to take static IP addresses that the novell servers are using now so, after i add the LA subnet in sites and services, then would i give server2 the exsisting IP address for the LA Subnet? And this server will be in the same domian but act as a separate domian controller just for users in LA right?
    0 pointsBadges:
    report
  • Natethegreat
    Also, would i have to make the server2 a primary DNS server because it is on another subnet and it is a domain controller? Currently the primary and secondary DNS servers are in SLC.
    0 pointsBadges:
    report
  • PaulHinsberg
    "Both servers are going to take static IP addresses that the novell servers are using now so, after i add the LA subnet in sites and services, then would i give server2 the exsisting IP address for the LA Subnet? " Yes, if you are done with teh novell server that is using the IP address. "And this server will be in the same domian but act as a separate domian controller just for users in LA right?" The server2 would be in LA. It would act as a domain controller for the domain you created. By creating the subnet and LA Site, the server2 would be in the SITE for LA. Thus, when users in LA perform Active Directory actions (searches for printers, authentication,etc) they would use the server in their site - which would be server2. "Also, would i have to make the server2 a primary DNS server because it is on another subnet and it is a domain controller? Currently the primary and secondary DNS servers are in SLC." The decision to make server2 the primary DNS server for the LA region is not mandatory, but makes perfect sense. For the server2 to be a primary for the region you DO NOT have to configure anything on the server aside from having installed DNS. You must reconfigure the IP configuration of all of the client and servers in LA to point to server2 first and server1 second. Hopefully, you are using DHCP for the clients making this an easy task.
    15 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following