dpacpa
asked on
OWA address fails internally but works externally
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, https://192.168.0.51/owa works, etc.
I don't know if this a firewall issue, or a DNS issue, or what.
Internally, I can get to it from many other variations of the address: https://exserver09/owa works, https://exserver09.mydomain.com/owa works, https://192.168.0.51/owa works, etc.
I don't know if this a firewall issue, or a DNS issue, or what.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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.
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.
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.
Don't mess around with split DNS unless you need to.
ASKER