Create Outlook Web Access Web Page Exchange 2007 - For Multple Domain Names
There are currently twodomains configured tosend and receive email on our exchange 2007, Win2k3 server: dom1.com and dom2.com. dom1.com is the default domain. I can access dom1.com and dom2.com at https://mail.dom1.com/owa and https://mail.dom2.com/owa.I am going to update the certificate and am doing some research on which names to include in the certificate.The company will be adding a third domain dom3.com, and maybe dom4.com.As I look through our internal DNS I do not see a Zone or Host A/MXrecords fordom2.com. I do see a zone created with MXand Arecord (internal ip address)for dom1.com and the MX record mail.dom1.com.WhenI researchpublic DNSI see the correct IPAddressassociated with the MX record forthe Exchange server for both dom1 and dom2.I do not understand how we are sending/recieving email for the second domain, dom2.com,internally/externally if there are no DNS records internally?I aslo do not understand how theurl and web siteis created for Outlook Web Access?I see no records in our internal DNS indicating there is anything located at https://mail.dom2.com/owa.Or that there is any additional web site created in addition to the default website. I am not sure where to look in IIS toverify current configuration for dom1 and dom2 so that i can create a url for dom3 and dom4?It's clear the resourceexists for dom1 and dom2 becuaseIcan open internet explorer and access the web siteinternally/externally. How is the web site created for OWA for each domain and how doI associatea URL to it?We are in the process of changing ouremail address from dom1.com to dom3.com.(dom2.comis a child domain of dom1.com in our internalactive directory. It's a subsidiary company) FurthermoreWeare sending email with the dom3.com name however theDNS MX recordstill resides at an ISP.The mail from dom2.comisforwardedfrom the ISP to the dom1.com domain (our exchange server), and sent from exchange using the dom3.com domain.So it appears that we are hosting the MX record even though weare only forwarding.I have read"How to configure exchange 2007 to accepte-mail formore than one authoritative domain""configure the client access server"White paper: Exchange 2007 autodiscover service"How to configure connectors for internet mail flow""How to configure internet mail flow through a subsribed edge transport server""how to configure mail flow between an edge transport server and hub transport servers without using edgesync""how to configure internet mail flow through exchange hosted services or an external smtp gateway""how to configure internet mail flow directly through ahubtransport server"joe - not a plumber
March 20th, 2009 3:58pm

Hi, As the internal sending email from the second domain (dom2.com), the message is submitted to the advanced queuing engine by using OWA or Outlook client through the store driver. The message categorizer then queries the global catalog server with the recipient address to find the user. If the recipient address is in a recipient policy, or if a matching recipient with a proxy address does exists (the recipient address will be stored in Active Directory), the message categorizer determines that the message is bound for a local delivery. Then the message categorizer makes an LDAP query to the global catalog server to find the homeMdb attribute of the recipient. The homeMdb attribute is the users home mailbox server, which is the location where the users mailbox store and mailbox reside. Finally, the Exchange store driver then delivers the message to the mailbox store. Thus, the A record and MX record is not used for the internal sending and receiving email. As the internal OWA for the second domain (dom2.com), if first tries to access the https://mail.dom2.com/owa by using A record in internal DNS, when that fails, it will turn to public DNS. To access OWA with multiple names, you can create another website under IIS, then specify the name as the Host header for the Web site. Please understand that IIS will need to figure out the right website to direct the request. This is done using either the Port, the IP address, or a host header. Thanks Allen
Free Windows Admin Tool Kit Click here and download it now
March 24th, 2009 10:19am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics