This is by design, since Windows DNS is local to your domain at home you
will resolve it by the FQDN of your computer on your home network. When you
are external to your Windows Domain you will have to resolve your domain by
the external DNS records created by your ISP, in this case Go Daddy. This
both secure and prefer method of keeping your External and Internal DNS
separate.
If you want to resolve your External DNS records internally, you will have
to add these records in DNS Manager. For example, your website A record at
Go Daddy will point to your Static IP. Create a www record for this static
ip in DNS Manager.

Signature
John Oliver, Jr
MCSE, MCT, CCNA
Exchange MVP 2006
Microsoft Certified Partner
> Hi,
> I noticed that when i try wireless active sync on my home network with
[quoted text clipped - 8 lines]
> https://domainname/exchange ot access OWA. At home i have to type
> https://computername.domainname/exchange
Lanwench [MVP - Exchange] - 26 Apr 2006 01:32 GMT
> This is by design, since Windows DNS is local to your domain at home
> you will resolve it by the FQDN of your computer on your home
[quoted text clipped - 7 lines]
> A record at Go Daddy will point to your Static IP. Create a www
> record for this static ip in DNS Manager.
With RPC over HTTP, I believe the same profile should work internally and
externally - specifying server.mydomain.local should work from the outside
because of the SSL certificate and the proxy settings in OL2003.... ?
>> Hi,
>> I noticed that when i try wireless active sync on my home network
[quoted text clipped - 8 lines]
>> web when i have to type https://domainname/exchange ot access OWA. At
>> home i have to type https://computername.domainname/exchange