How to setup IP address for DC&ADC

Question

Hello ,
I have DC server and ADC server I need to configure IP address for both server
correctly ,kindly tell me  how do that.
because I have problem : on DC server computer container is empty all computer in my network
appear in ADC however if you search for any computer in DC I can find it
Note: If you have created any user in the server immediately user appear on the other server
thanks

Answer 1

I see, you are worried about what would happen with your Exchange server if one of your DCs go down.
That's not an easy question to answer. It's a very complex question because there are multiple components at play.
First, let's discuss the client side resolver. Each operating system has one no matter if it's a DC, server, workstation, Apple, Unix, Linux, Android, etc. The way they work is based on the industry standard RFCs that explain how they work.
The client side resolver will only look at the second DNS entry if the first entry returns a NULL response (no response) after a time out period. However, if the client side resolver already has the record cached (you can see the cache by running ipconfig
/displaydns) for the TTL of the record, and the DC goes down, well the client side resolver will not query again because it sees it already has it in cache.
Exchange will automatically look for another LDAP, Config and GC if the one it's using goes down. However, Outlook isn't so forgiving. It locks on to a GC and a DSProxy for the Exchange server. If the GC goes down, you have to restart Outlook. That's going
to be difficult if you have lots of users.
And if Exchange is on a DC, that doesn't work that way because it *locks* on to the DC/GC it's installed on. I hope your Exchange server is not on a DC.
Here's more specifics on how the whole process works - and note that this applies to all operating systems, Windows, Linux, Unix, BEOS..... because they all follow the RFCs defining how client side resolvers work.
This blog discusses:
WINS NetBIOS, Browser Service, Disabling NetBIOS, & Direct Hosted SMB (DirectSMB). Troubleshooting the browser service.
Client side resolution process chart.
The DNS Client Side Resolver algorithm.
If one DC or DNS goes down, does a client logon to another DC or use the other DNS server in the NIC?
DNS Forwarders Algorithm and multiple DNS addresses (if you've configured more than one forwarders or more than one IP in the NIC's DNS list)
Client side resolution process chart
Published by Ace Fekay, MCT, MVP DS on Nov 29, 2009 at 10:28 PM  1764  1
http://msmvps.com/blogs/acefekay/archive/2009/11/29/dns-wins-netbios-amp-the-client-side-resolver-browser-service-disabling-netbios-direct-hosted-smb-directsmb-if-one-dc-is-down-does-a-client-logon-to-another-dc-and-dns-forwarders-algorithm.aspx
DNS Clients and Timeouts (Part 1 & Part 2), karammasri [MSFT] Dec 2011 6:18 AM
http://blogs.technet.com/b/stdqry/archive/2011/12/02/dns-clients-and-timeouts-part-1.aspx
http://blogs.technet.com/b/stdqry/archive/2011/12/15/dns-clients-and-timeouts-part-2.aspx
DOMAIN NAMES - CONCEPTS AND FACILITIES - Dicusses local resolvers.
http://tools.ietf.org/html/rfc882
Ace Fekay
MVP, MCT, MCSE 2012, MCITP EA & MCTS Windows 2008/R2, Exchange 2013, 2010 EA & 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php
This posting is provided AS-IS with no warranties or guarantees and confers no rights.