Solved

Installing DNS on the additional DC???

Posted on 2009-05-06
6
246 Views
Last Modified: 2012-05-06
Dears,

I need to have a redundancy to my DNS. I have 2 DC's as follow:

One act as the main DC and DNS configured on it and the another DC act as its additional but without DNS.
Dears,

I need to have a redundancy to my DNS. I have 2 DC's as follow:

One act as the main DC and DNS configured on it and the another DC act as its additional but without DNS.

I need to configure a secondary DNS on the additional DC. Is it recommended to create
I need to configure a secondary DNS on the additional DC. Is it recommended to create it as an active directory integrated or secondary zone pointing to the primary one only?

Please recommend a solution for me?
0
Comment
Question by:bateg
6 Comments
 
LVL 70

Accepted Solution

by:
KCTS earned 300 total points
ID: 24312563
No need to get boggged don in "Primary" and "Secondary". If you are using AD Integrated DNS (the default), then all you have to do is add the DNS server service on the second DC, DNS will rplicate along with AD and tou will in essence have multiple primary DNS servers.

You will of course need to configure the clients to use on DNS server as the preferred DNS server and the other as the alternate DNS server. - The DCs should use themselves as their own preferred DNS server and each other as alternate.
0
 
LVL 18

Expert Comment

by:Americom
ID: 24314294
In addition to install DNS service on your second DC, you need to create the exact same zone name(s) on your secondary DNS and configure them as Active Directory-Integrated zone(s). Before you even do the configuration, you should double check and make sure your current DNZ zone is configured as Active Directory-Integrated zone first.
Since you have only two DCs, one other thing you may want to do is make your second DC also a GC, if it is currently not a GC.
0
 
LVL 27

Assisted Solution

by:bluntTony
bluntTony earned 200 total points
ID: 24314307
As KCTS has said, just install DNS and either initiate replication, or wait for it to occur. You will see the DNS zones drop into the console of the new DNS server. Once replication has occurred you can change the new DC's primary and secondary DNS servers.

While setting a DC to use itself as primary DNS I think is the generally accepted rule, there are arguments for and against this. For example, if you do get each DC to look at itself for DNS primarily, and for some reason you change one of the DCs IP address, that change will never replicate, causing a 'DNS Island' - a catch 22 where the other DC needs the other's IP to replicate, but it won't know it until it replicates.

This is just an example really, and probably unlikely. I personally configure my DCs as KCTS has said. Have a look at this for the MS best practices for DNS : http://support.microsoft.com/kb/825036
0
Is Your AD Toolbox Looking More Like a Toybox?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

 
LVL 27

Expert Comment

by:bluntTony
ID: 24315709
Americom - I have to respectfully disagree. Providing that the DC is in the replication scope of the ADI DNS zone (being in the same domain it should be, whether it's the domain NC or DomainDNSZones), the zone will replicate and drop into the console automatically. It'll take a few minutes but it does come in by itself. At least in does in my W2K3 test environment.
I can't help thinking that manually creating a duplicate zone in the directory might cause some problems.
0
 
LVL 70

Expert Comment

by:Chris Dent
ID: 24316620

> I can't help thinking that manually creating a duplicate zone in the directory might
> cause some problems.

You'd be right.

If it's in the same partition it can overwrite an existing copy (sometimes, not always, depends which has the "latest" version). If it's in a different partition it can cause the DNS server to become rather upset about finding multiple copies of the same zone.

Install the DNS service, wait for replication. The data is there, nothing needs to be created, it just needs time to think about loading it.

Chris
0
 
LVL 18

Expert Comment

by:Americom
ID: 24317546
I totally agree that install the dns services and wait for replication or just force replicaiton manually would get the data, afterall, this is active directory-integrated zone and I have personally done it many times. What was I thinking or writing, primary/secondary zone??....no excuse! Thanks for pointing out the mistake, wish I can grant some point to you :)
0

Featured Post

Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

While rebooting windows server 2003 server , it's showing "active directory rebuilding indices please wait" at startup. It took a little while for this process to complete and once we logged on not all the services were started so another reboot is …
This script can help you clean up your user profile database by comparing profiles to Active Directory users in a particular OU, and removing the profiles that don't match.
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …
This video shows how to use Hyena, from SystemTools Software, to bulk import 100 user accounts from an external text file. View in 1080p for best video quality.

786 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question