Resolving External Address of Internal Server Internally
Posted on 2012-08-23
I have a Windows Server 2003 R2 server running Exchange 2007. Users externally can connect with OWA or Outlook or Activesync just fine. However when users try to connect inside the office on the same subnet, they are not able to connect to the external address of the server (i.e. mail.xxxcompany.com). They can resolve the local server name just fine on their phones' web browsers, but their Activesync setup can only resolve one address and it's set up as the external address.
This is a single server environment which I set up nearly ten years ago. I was dumb enough to use the same external DNS name as the internal DNS name as well. The AD Domain is also xxxcompany.com.
I'm also having trouble with NSLOOKUP failing too. I'm not sure if this is related, but I'm getting this error:
*** Can't find server name for address 192.168.1.2: Non-existent domain
Default Server: UnKnown
I tried the traditional fix to this, but no luck.
I have the server pointing to it's local address as the DNS server.
It's been a while since I worked with Windows Server 2003 so IP 6 isn't the issue here.
So two questions:
1. How would I set up the external address for the email server to be resolved internally so that users can connect with their Droid and iPhones in the office?
2. How can I resolve the NSLOOKUP issue?