OWA address fails internally but works externally

Posted on 2010-01-12
Medium Priority
Last Modified: 2012-05-08
I have a new Exchange Server 2007.  Things seem to be okay except for OWA.  When I log in from an external connection to the URL - https://www.mydomain.com/owa, I get to the site.  When I log in from an internal PC, the page cannot be displayed.

Internally, I can get to it from many other variations of the address: https://exserver09/owa works, https://exserver09.mydomain.com/owa works, works, etc.

I don't know if this a firewall issue, or a DNS issue, or what.
Question by:dpacpa
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
LVL 13

Assisted Solution

NarendraG earned 400 total points
ID: 26296243
yes it is purely DNS issue

may be your web site hosted outside

as your dns server pointing to that address

do a nslookup with domain name  see to where  ip address it pointed

even you can add ptr record in dns server also

Good Luck
LVL 74

Accepted Solution

Glen Knight earned 1600 total points
ID: 26296316
Do you have a forward lookup zone on your internal DNS for mydomain.com?

If so make sure you have an A record for www in there.

You may have to create a split DNS so that you do have an internal zone because your router may not allow you to loop back to it's IP address.

What you are seeing is quite normal.

Author Closing Comment

ID: 31676272
Thanks a lot guys!
LVL 13

Expert Comment

ID: 26296508
To avoid any conflicts in future, I would suggest that you get a URL such as mail.mydomain.com for OWA.

I am suggesting this in case you have a website hosted for mydomain.com
You can then create Host 'A' record 'mail' in internal and external DNS as well.

In case you do not have any external website hosted for "mydomain.com" you can then directly create a blank Host A record in the internal DNS in the zone "mydomain.com" and point it to the Exchange Server.

I am suggesting a blank Host A record instead of 'www' as suggested by demazter as then you can resolve both 'www.mydomain.com' and 'mydomain.com' to the same website i.e. OWA

P.S: If you do not have a Forward Look Up Zone in your internal DNS for "mydomain.com" then you will need to create one.
LVL 74

Expert Comment

by:Glen Knight
ID: 26296536
Personally I would just add a favourite using Group Policy to use the internal name.

Don't mess around with split DNS unless you need to.

Featured Post

On Demand Webinar: Networking for the Cloud Era

Ready to improve network connectivity? Watch this webinar to learn how SD-WANs and a one-click instant connect tool can boost provisions, deployment, and management of your cloud connection.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article explains how to install and use the NTBackup utility that comes with Windows Server.
This article will help to fix the below error for MS Exchange server 2010 I. Out Of office not working II. Certificate error "name on the security certificate is invalid or does not match the name of the site" III. Make Internal URLs and External…
In this video we show how to create a mailbox database in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Servers >> Data…
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…
Suggested Courses

770 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question