Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Backup DNS 1

Status
Not open for further replies.

cc929

IS-IT--Management
Nov 21, 2003
127
US
Hi all,

I have DNS server in the w2k DC and would like to add the backup DNS server in the w2k3 server with exch2003.

Does anyone can show me how to setup backup DNS server?
Is it a good place add backup DNS server in exch2003?

Please advise!

Many thanks in advance!

cc929
 
Dear monsterjta,

That's mean when I backup system state, I will also backup DNS. Is it correct?

If I would like to setup secondary DNS server, how can I do it?

THanks again!

cc929
 
Setup a second domain controller. If you DNS zone is Active Directory integrated, it will then be replicated to your second Active Directory server. If anything should happen to your first server...your second server can still be used.

In the case you lose your first server, you would just need to replace or rebuild it and then once it is a domain controller again...it will replicate the information from your second domain controller.

A backup of the system state may not backup the DNS. The DNS information, if not AD integrated will be found in ".dns" files on the system. If it is AD integrated, then the information will be found in the Active Directory databases.
 
Dear kbing,

Thanks for your information!

If I would like to setup secondary DNS server, in case the primary one has problem.

How can I setup secondary DNS server on different server?
Is it a good idea to setup secondary DNS server at Exchange 2003?

Please advise!

cc929
 
As kbing has stated, if your dns zone is Active Directory integrated, just bring up a second domain controller in your domain and install dns as active directory integrated. Now this second domain controller can act as a dns server.

In order to run dns you would need to make your exchange 2003 box a domain controller. In my opinion, it is not a good idea to run exchange on a domain controller.

Jim W MCSE CCNA
Network Manager
 
Ditto on the strategy of NOT making your Exchange server a domain controller. This leads to problems down the road.

You have two options for making a secondary DNS server. As we stated, the first option is to setup another DC with DNS. Ensure the DNS is AD integrated...and your done because when AD replicates the database...it also replicates DNS.

If you want the more traditional Primary / Secondary DNS, you can setup a server with "just" DNS services. Then create a secondary zone to "pull" the DNS zone from the primary. Be sure to enable zone transfers on the primary DNS server.

This will essentially allow you to copy the zone to another system automatically but will not help you if you lose your domain controller because the new DNS server cannot do any authentication.

I still recommend making it a second DC (if you don't already have 2 DC)'s. That way you get an insurance policy for both AD database and DNS.
 
Thanks for all your help!

cc929
 
I'll add that you CANNOT PROMOTE OR DEMOTE A SERVER THAT ALREADY HAS EXCHANGE ON IT. Doing so permanently breaks Exchange.

Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top