interc3905
asked on
Config exchange server for Intranet and Internet access
I know there is a simple solution but having trouble finding it - mainly because I probably don't know terminology. Here is the simple issue.
We have Exchange server that works fine with MANY email domains running on it. We setup all the MX records to be mail.domain.com and their POP server works via Internet outside our network. However if we connect to our internal network with same laptop - the mail.domain.com will not work, but the private IP of the email server will. So we are having a DNS issue somewhere. Editing the HOST file on the PC works for PCs that stay inside office but it is a pain for laptops having to change incoming server from mail to ip and vice versa.
So I guess I need step by step for an Exchange 2003 for "shadow" DNS entry at the server layer?
We have Exchange server that works fine with MANY email domains running on it. We setup all the MX records to be mail.domain.com and their POP server works via Internet outside our network. However if we connect to our internal network with same laptop - the mail.domain.com will not work, but the private IP of the email server will. So we are having a DNS issue somewhere. Editing the HOST file on the PC works for PCs that stay inside office but it is a pain for laptops having to change incoming server from mail to ip and vice versa.
So I guess I need step by step for an Exchange 2003 for "shadow" DNS entry at the server layer?
Amit
How many NIC's you have on this server?
ASKER
One
Can you run nslookup and check the result.
ASKER
nslookup resolves to Internet address inside and out
That's not correct. It should resolve to server name.
ASKER
nslookup is not the issue; it produces the right ip address for our server via MX record for that domain. It does it outside our network and inside our network.
No that is not right. Internally, it is should point to server name not to external dns record, that's why internal users are unable to connect to Exchange server.
ASKER
Internet users are able to connect to Exchange server by internal ip address only. nslookup resolves the MX record domain name to the external static ip. Using the mail.domain.com or external ip inside the NETWORK does not work. I want that to work so no matter where the laptop is - in or out - it works with mail.domain.com.
It is time for you to upgrade to Exchange 2010. Which has autodiscovery feature and you can configure same fqdn for internal and external users.
ASKER
So how do you do that with Exchange 2010? I have that issue at another location also and they do have Exchange 2010.
ASKER
I resolved the issue; you have to make sure each PC's primary DNS on LAN is pointing to internal ip of gateway instead of the ISP DNS #s. Then on the server go in to the DNS Manager and add an A record for mail.domain.com and point it to the LAN IP of the server itself. Walla. Email now resolves domain name inside and outside network. Knew there had to be a simple answer other than just upgrade to 2010 Exchange.
ASKER
I've requested that this question be closed as follows:
Accepted answer: 0 points for interc3905's comment #a40777925
for the following reason:
No one answered my question accurately - only offered Plan B.
Accepted answer: 0 points for interc3905's comment #a40777925
for the following reason:
No one answered my question accurately - only offered Plan B.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Still would have to add A records to DNS Server so you were partly right.
Thanks for the point :)