Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

Is there a way I can set an OWA server in my DMZ to talk to a DC in the local site?

The DMZ is located at the same (physical) site as a LAN with DCs on it. (There is no DC in the DMZ.)

Can I force it to use a DC on this (local) subnet, as its picking random ones at the other side of the world!

share|improve this question
    
What version of Exchange Server are you running? –  joeqwerty Oct 5 '11 at 14:23

2 Answers 2

up vote 11 down vote accepted

You need to define AD Sites in Active Directory Sites and Services. You then specify what subnets define each site. Then you can assign Domain Controllers to that site.

If you have a world-wide distribution of the same AD Domain, you should absolutely set this up, because not only are your mail servers using random DCs across the world, but your workstations are as well.

share|improve this answer
    
It's amazing how many people don't set this up properly!! –  Aceth Oct 5 '11 at 15:03
    
Sites are set up already - but it's still picking up seeming random servers. –  Ben Oct 5 '11 at 21:22
2  
@Ben, then it's not set up correctly in all likelihood. –  MDMarra Oct 5 '11 at 21:37

Configuring sites is of course a good start. However you should still be aware that you cannot "force" the usage of a specific DC using Sites and Services. This is by design. For example, if the DC in your site is down, Windows should try a DC in another site.

If you have a topology with a main location (such as HQ or datacenter) and remote "spoke" sites with DC's that only need to perform local authentication and other DC functions, the remote DC's can be configured to not advertise certain services by using the DnsAvoidRegisterRecords registry setting.

Also note that you can influence preference order by using the Priority and Weight of the SRV DNS records in the _msdcs subdomain, but that should only be done after a thorough analysis. Clients attempt to contact the server with the lowest priority. Weight is a load-balancing mechanism that is used when selecting a target host from those that have the same priority. Clients randomly choose SRV records that specify target hosts to be contacted, with probability proportional to the weight.

More information:

How to optimize the location of a domain controller or global catalog that resides outside of a client's site
http://support.microsoft.com/kb/306602

SRV Resource Records
http://technet.microsoft.com/en-us/library/cc961719.aspx

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.