DNS in two DCs

Microsoft Windows server 2003
February 16, 2010 at 08:53:22
Specs: 2003
Have configured two DCs. While running DCPROMO on one, installed DNS as part of it however did not install DNS while installing second DC. Later, If first DC goes down second would not work. Ofcourse, because DNS is not there on this DC. Can any body help to configure DNS on this server manually?

My Second Question is:

What else required for getting users to successful login if i do not transfer roles to second DC incase first is down.

See More: DNS in two DCs

Report •

February 16, 2010 at 10:53:31
rules of thumb

1. both dc had dns server as either primary/secondary or ad intergrated. You can install the dns server on the 2nd dc any time you want.

2. both should have the global catalog.

3. With 2 dc's I wouldn't worrry about the fsmo roles. You can always seize them.

4. Consider engaging FRS and DFS to provide data redundancy between the servers

Report •

March 6, 2010 at 08:53:01

Thanks for the info..

DNS thing is sorted out. Can you please give me some idea abt difference between transfering and seizing. What i understand is while both DCs are live then it is called transfer, right? but what happens in seizing?


Report •

March 6, 2010 at 09:25:48
In an Active Directory domain, I would recommend using AD Integrated domains vs using a primary/secondary setup.

If you install DNS on the second DC and select AD Integrated, you are done. The DNS information will replicate between the two DCs and you are pretty much done. Set up your clients to have one of the DCs as their preferred DNS server and the other one as the alternate.

You transfer a FSMO role while the servers are up and running.

You seize a role when one of the DCs in down and unable to be repaired and not intended to come back online again. Some articles recommend never bringing a DC that had a role seized back up on the network again. This isn't necessarily required but isn't a bad idea.

Basically the difference between transferring and seizing is that transferring is a planned and voluntary act. Seizing is done usually because of a catastrophic failure of a DC and the role must be seized. It can't be transferred because the DC currently holding the role is unavailable.

Report •

Related Solutions

March 6, 2010 at 23:30:31
Thanks for all your help on DNS.

Since we are discussing about DNS, i had query about DNS if somebody can help me out. Would like to get more and more views on this..
MY Query is, I work for BPO where are so many process use their applications and internet. We are using squid proxy to access the internet. Some times we get calls that applications are running slow. I want to check how much is proxy resposible for internet access and how much DNS?

What I understand is DNS is for name resolution and proxy is just for access. If i try to resolve some website name using DNS, can it be blocked by proxy?

Have confusion about this. would really appreciate if somebody can make me understand?

Report •

Ask Question