Converting secondary DNS server to Primary
I recently was hired as a Network Administrator at a small company with ALOT of network problems. I have rebuilt most of the network due to a Corrupt Active Directory, Bad hardware etc. Now to get to the point. My predecessor made the Terminal Server the primary DNS server. This was because he had a VERY corrupt Active directory on the PDC. I established a working Active Directory and made the PDC a seconday DNS server. I want to make the PDC the primary DNS server and remove the Terminal Server from this function. How do I go about doing this?
This is my first time using this forum and I appreciate any help that you could give me regarding this subject.
Best Regards
Mike
This is my first time using this forum and I appreciate any help that you could give me regarding this subject.
Best Regards
Mike
ASKER
Jay
When I built the PDC I made sure that DNS was replicating with the Terminal server DNS machine. So am I to understand that all I have to do is uninstal the DNS service from the Terminal Server and that is it? How do I convert the PDC to the primary DNS server? When you set up DNS you must state whether the machine will be primary or seconday. How do you promote it to primary.
All froward and reverse znes are fine.
When I built the PDC I made sure that DNS was replicating with the Terminal server DNS machine. So am I to understand that all I have to do is uninstal the DNS service from the Terminal Server and that is it? How do I convert the PDC to the primary DNS server? When you set up DNS you must state whether the machine will be primary or seconday. How do you promote it to primary.
All froward and reverse znes are fine.
The primary DNS server is denoted by the holder of the start of Authority (the SOA) record. You can change this yourself in the SOA record details.
The most important part of this puzzle is your DHCP and making sure that you change that to where that the clients get the correct information. Due to the time of DHCP usually have a large time frame 7 days or such.. you need to make sure that your clients are pointing to the proper DNS before you stop DNS on the system they are looking at.. which in this case I believe is your term serv. You can also make the necessary changes in DHCP and then reboot your clients.. this should work, but you need to verify. If you simply take DNS of the server they are using, you'll quickly see they can no longer connect to anything!! This is a bad thing. The settings you see when installing AD and in DNS are only for those machines.. you must configure your DHCP to properly give out the DNS server information to your clients.
mike,
pretty much mate, Keith's comments on the SOA will help you if you have any issues, but a lot of the time you dont even need to touch that record (just my experience so far) always best to have a clean directory though so you may as well change it
pretty much mate, Keith's comments on the SOA will help you if you have any issues, but a lot of the time you dont even need to touch that record (just my experience so far) always best to have a clean directory though so you may as well change it
ASKER
All of you have made some good points. I had set up the network on static IP's so I dont have to worry about DHCP. How do I change the SOA details? Do I uninstall the DNS from the Terminal server and then adjust the SOA details? What are the steps I should follow?
I really appreciate all of you taking the time out to help me like this
Mike
I really appreciate all of you taking the time out to help me like this
Mike
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Mike, can you confirm the version of operating system you are running?
Also, can you confirm that you are definitely ruuning AD-Integrated or primary/secondary?
Only reason for asking is that the process is slightly different.
Also, can you confirm that you are definitely ruuning AD-Integrated or primary/secondary?
Only reason for asking is that the process is slightly different.
ASKER
Keith:
We are running Windows 2000 server on the PDC and Terminal Server. I have AD properly installed and running on the PDC and it is correctly replicating the forward and reverse lookup zones dound on the Primary DNS server (the Terminal Server).
I appreciate all your help
Mike
We are running Windows 2000 server on the PDC and Terminal Server. I have AD properly installed and running on the PDC and it is correctly replicating the forward and reverse lookup zones dound on the Primary DNS server (the Terminal Server).
I appreciate all your help
Mike
ASKER
My DNS server is NOT Active Directory Integrated. Although the PDC has a functioning Active Directory, the DNS is not Active Directory integrated.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I got the job done. Everything is running smooth. I will split the points among you. Keith will be receiving the greater share, followed by Jay.
Best Regards
Mike
Best Regards
Mike
Thanks Mike. Glad you have it the way you want it.
Regards
keith
Regards
keith
thanks mate, sorry i didnt post for a while - im in Aus and was in bed....
lol, and I'm just going.... its 10.45PM and I'm tired. :)
best way is to make sure that your dns zones are active directory integrated. you will find that DNS is installed on the Domain Controller currently anyway Active Directory wont run unless DNS is installed locally. You just need to make sure the DNS is replicating and to remove DNS from the term serv, simply uninstall - it is always good to have a secondary DNS server though. Just make sure the clients are pointing to your DC as primary DNS
Cheers!