If DC goes down, how clients will automatically go to ADC

Hi All,

I have a DC environment in which i am also running an AD integrated DNS.

Just to add redundancy i added one more ADC in the current environment and joined it to the existing domain while running the setup of dcpromo. Active directry database on the DC was successfully replicated on the ADC and i can see all the objects in ADC. Then i installed DNS on ADC, and it also gets synchronized with the master DNS at DC, getting all the DNS records from there.

Now, i am confused that how can i add redundancy at client end. If DC goes down, how clients will automatically go to ADC.
mahtab786_dbiAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

flyingskyCommented:
I don't quite get it. Do you mean you just added another Domain Controller to the domain, or you mean you added an Active Directory Connector?
If you just added another DC, then all you need to do is to configure the new DC in your DHCP as a secondary DNS server. You may need to consider set it up as another DHCP server though
0
craigothyCommented:
Basically, you just need to make sure you hand out a secondary DNS server (of your newly created DC) to all of your clients either statically or by updating your DHCP scope options.  
0
Mike KlineCommented:
In addition to the DNS settings that craig and flying mentioned make sure to make the new DC a global catalog server too.
If you want the down and dirty details of how domain controllers are located take a look at
http://support.microsoft.com/kb/247811
How Domain Controllers Are Located in Windows
Thanks
Mike
 
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

mahtab786_dbiAuthor Commented:
Hi mike,
I am agree with u to make the new dc a gcs...so if main(first) dc will be down..clients will go automatically to another DC...
0
Mike KlineCommented:
Yes but you have to make sure to add the new DC /DNS server as their secondary DNS server like the other guys mentioned.
You can test this out during your next patching cycle.  (because I know the machine will need to be rebooted anyway)
Patch the first one and shut it down.  Make sure you can login from a few machines.  Just so you know it works.  Then power it back on.
Thanks
Mike
0
craigothyCommented:
One other thing I would suggest in case you haven't do so already, is to make DC1's primary DNS server itself and the secondary as DC2.  Also, on DC2 make its primary DNS server itself and its secondary DC1.  That way DC1 will still be able to resolve DNS itself in the case that DC2 is offline and vice versa.
0
mahtab786_dbiAuthor Commented:
ok fine.........now I have 2 doubt.........first as I mentioned in my question i have installed DNS on another DC, and it also gets synchronized with the master DNS at DC, getting all the DNS records from there.so no need to do more with dns on another dc.

second thing how clients will get IP Address as DHCP is configured on First DC.
0
amichaellCommented:
Utilize two DHCP servers with their own scopes making sure the scopes do not overlap in regards to the IPs they hand out.  So, SERVER1 might hand out 172.17.70.0/24 addresses while SERVER2 might hand out 172.17.30.0/24 addresses.
0
Mike KlineCommented:
If you do go with another DHCP server you can also go with a 80/20 or 70/30 split
http://technet.microsoft.com/en-us/library/cc958936.aspx
How long are your leases set for right now?  If it is the default of 8 then clients have some time before you have to worry about that.  
Yes with AD integrated DNS the info gets replicated
 
Thanks
Mike
0
Brian PiercePhotographerCommented:
You are on the right lines
If you have Installed Active Directory on the new Machine then if you add the DNS server role, then DNS will be automatically replicated

You MUST make sure BOTH DCs are Global Catalog Servers

If you are using DHCP then the simplest way to configure this is to set-up and authoirise both machines as DHCP servers and configure
each server with non-overlapping roles eg set one DHCP server to use IPs 192.186.1.100 - 192.168.1.150 and the other to use 192.186.1.151 - 192.168.1.200

You must also configure clients to use one machine as the preferred DNS server and the other as the alternate DNS server, for machines with static IPs you can the DNS servers in the TCP/IP properties. for machines that use DHCP, then you need to add both DNS servers DNS server options in the DHCP console - on both DHCP servers.

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
AhmedCharaniaCommented:
In case of primary DC down, you will need to transfer FMSO roles to newly added DC.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.