TCP/IP setting of Domain Controller at different sites

Hi have the following setup with TCP/IP setting in the below addresses.
Will that be any issue with replication? i have address a new site on the AD site & Services.  
On the DNS server, how should i setup?

Site A
Domain Controller A   -  IP address 192.168.1.10 /24 Primary DNS 192.168.1.11 Secondary DNS 192.168.1.10
Domain Controller B    - IP address 192.168.1.11 /24 Primary DNS 192.168.1.10 Secondary DNS 192.168.1.11

Remote Site B
Domain Controller C    - IP address 192.168.2.10 /24 Primary DNS 192.168.2.11 Secondary DNS 192.168.2.10
Domain Controller D    - IP address 192.168.2.11 /24 Primary DNS 192.168.2.10 Secondary DNS 192.168.2.11
LVL 1
dnackAsked:
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.

Seth SimmonsSr. Systems AdministratorCommented:
all four should point to itself first and the other server in the same site second
intersite replication should work fine
0
dnackAuthor Commented:
Hi Seth Simmons,

point to itself and point to loop back address is it the same? I saw some MS article that never use the loop back address as the primary.

http://technet.microsoft.com/en-us/library/ff807362%28v=ws.10%29.aspx

Can explain why you chose to point to itself first?
0
Seth SimmonsSr. Systems AdministratorCommented:
if server A points to B first and B goes down, could be a minor delay waiting for a first response from server B that could trigger some warnings in AD
probably not a huge deal, just something to keep in mind
and yes, best practices analyzer for AD will flag a warning if the loopback is DNS primary
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

MaheshArchitectCommented:
You should point DCs own IP (Not loop back address) as primary
0
George SasIT EngineerCommented:
Your config should look like this :

Site A
Domain Controller A   -  IP address 192.168.1.10 Primary DNS 192.168.1.10 Secondary DNS 192.168.1.11
Domain Controller B    - IP address 192.168.1.11 Primary DNS 192.168.1.11 Secondary DNS 192.168.1.10

Remote Site B
Domain Controller C    - IP address 192.168.2.10 Primary DNS 192.168.2.10 Secondary DNS 192.168.2.11
Domain Controller D    - IP address 192.168.2.11 Primary DNS 192.168.2.11 Secondary DNS 192.168.2.10

In the sites and services you will have two sites, A and B.
Configure replication for DCA to replicate with DCB (this should be by default) , DCC and DCD.
DCB should replicate with the other 3 and so long.

Check your firewall rules if you have any firewall between the sites to allow RPC replication.
Here is a nice article regarding this :
http://social.technet.microsoft.com/wiki/contents/articles/584.active-directory-replication-over-firewalls.aspx

If RPC not possible then configure it to replicate using IP and set the replication costs between the sites to fit your bandwidth needs.

Hope this helped.

Regards

George
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
DrDave242Commented:
It honestly won't make much difference whether each DC points to itself or the other DC in its site as its preferred DNS server. By default, when a Windows machine issues a DNS query, it waits for all of one second for the preferred server to respond before issuing a second query to the alternate server (and possibly other servers), so that delay really isn't significant. The important thing is that you have them both in there. This is discussed in excruciating detail here, where you'll also learn that the preferred server isn't always queried first.

In addition, you may want to add the servers at the other site as additional DNS servers. If a power outage or other event brings down both DCs at one site, they're both going to experience startup delays if they're only using each other and themselves for DNS, and these delays will be measured in minutes rather than seconds. This is explained at length here. For the same reason, you shouldn't ever reboot both DCs at a site at the same time.
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
Windows Server 2008

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.