DNS did not resolve exchange .local record

i have an exchange server with server.loca name and i have installed the ssl UCC certificate and the autodiscover is working properly but   am getting  this error in Outlook connectivity test  

Untitled.png
mohammed-khalafAsked:
Who is Participating?
 
R--RConnect With a Mentor Commented:
Do you have a DNS host A  ex-mail.server.local  record on public dns.
The record  ex-mail.server.local should not be in the public dns. The record should be mail.domain.com and autodiscover.domain.com and pointed to public IP of the firewall and nat to the server internal IP.

Once you create the A records you have to configure the virtual directorie with mail.domain.com

check this article from http://www.msexchange.org may help you.

http://www.msexchange.org/articles-tutorials/exchange-server-2010/management-administration/exchange-autodiscover-part2.html
0
 
R--RCommented:
Server.local is for the internal domain. Please include the external name as mail.domain.com in SSL certificale and configure the Exchange virtual directories and OA. Also create the host A record mail.domain.com and point it to public IP of the firewall.
0
 
mohammed-khalafAuthor Commented:
i did all the SAN names in the ssl
autodicover.domain.com
dmain.com
mail.domain.com
but how to create host record with mail.domain.com??
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

 
mohammed-khalafAuthor Commented:
i configured the virtual directory address in the ECP  mail.domain.com
0
 
R--RCommented:
You have to create it with your DNS hosting provider.
0
 
R--RCommented:
OWA, ACtivesync, OA also configure autodiscoveruri in clientaccessserver
0
 
R--RCommented:
Set-ClientAccessServer -Identity "server" -AutoDiscoverServiceInternalUri https://mail.domain.com/autodiscover/autodiscover.xml
0
 
R--RCommented:
Get-WebServicesVirtualDirectory | Set-WebServicesVirtualDirectory -InternalUrl https://mail.domain.com/ews/exchange.asmx -ExternalUrl https://mail.domain.com/ews/exchange.asmx
0
 
mohammed-khalafAuthor Commented:
https://mail.domain.com/autodiscover/autodiscover.xml     (test resullt)

This XML file does not appear to have any style information associated with it. The document tree is shown below.
      <Autodiscover><Response><Error Time="03:41:49.2031191" Id="3970427709"><ErrorCode>600</ErrorCode><Message>Invalid Request</Message><DebugData/></Error></Response></Autodiscover>
0
 
mohammed-khalafAuthor Commented:
i did not understand the comment ID: 40552672
0
 
mohammed-khalafAuthor Commented:
i tryed to run the commend but no ues
0
 
mohammed-khalafAuthor Commented:
OK in Autodiscover test
         Autodiscover settings for Outlook connectivity are being validated.
       The Microsoft Connectivity Analyzer validated the Outlook Autodiscover settings.
       
But RPC /HTTP Still
      Additional Details
      Testing RPC over HTTP connectivity to server ex-mail.server.local
       RPC over HTTP connectivity failed.
       
      Additional Details
       
Elapsed Time: 139 ms.
       
      Test Steps
       
      Attempting to resolve the host name ex-mail.server.local in DNS.
       The host name couldn't be resolved.
        Tell me more about this issue and how to resolve it
       
      Additional Details
0
 
mohammed-khalafAuthor Commented:
we made the virtual directories to use the public domain name and we have A record in the zone file in the internet and autodiscover & MX,,    and forwarded  the ports the exchange and we have internal MX record and  in the internal network

any one can help me though teamviewer  i can give access
0
 
mohammed-khalafAuthor Commented:
we added an host record with the mail.dmainname.com and we pointed the IP address the public ip address
0
 
mohammed-khalafAuthor Commented:
it is working now we added an Host record with mail.domain.com and we pointed to the Public IP Address

Many Thanks
0
 
R--RCommented:
Thank you. I am glad that it helped you.
0
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.

All Courses

From novice to tech pro — start learning today.