Exchange Server 2003 Name Issue - Domain.local
Hi All,
I’m trying to resolve an exchange 2003 naming issue, but was not after to find a solution after research everywhere.
This is what happens, when setting up email account for exchange server.
Under Outlook 2003 -> Email account -> Exchange Server Settings:
If we enter “exchange.domain.com or IP address for the exchange server” -> Click check name, it will find the user account. However, the Exchange name will automatically change to “exchange.domain.local”.
We would like to use either “exchange.domain.com” or “IP address” BUT “exchange.domain.local” for a group of users. But, it just keep changing it back.
Below is some info about our environment
Server name is: exchange 2003 SP1
DC is: Windows 2003
Domain is: domain.local
Exchange server is a member of “domain.local” domain.
OWA and exchange are in the same server.
DNS: exchange.domain.com (DNS should setup correctly)
POP3 and OWA users can use either exchange.domain.com or IP address without problem.
Thank you in advance for all the help.
I’m trying to resolve an exchange 2003 naming issue, but was not after to find a solution after research everywhere.
This is what happens, when setting up email account for exchange server.
Under Outlook 2003 -> Email account -> Exchange Server Settings:
If we enter “exchange.domain.com or IP address for the exchange server” -> Click check name, it will find the user account. However, the Exchange name will automatically change to “exchange.domain.local”.
We would like to use either “exchange.domain.com” or “IP address” BUT “exchange.domain.local” for a group of users. But, it just keep changing it back.
Below is some info about our environment
Server name is: exchange 2003 SP1
DC is: Windows 2003
Domain is: domain.local
Exchange server is a member of “domain.local” domain.
OWA and exchange are in the same server.
DNS: exchange.domain.com (DNS should setup correctly)
POP3 and OWA users can use either exchange.domain.com or IP address without problem.
Thank you in advance for all the help.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
As already pointed out, what you are seeing is normal behaviour.
Lets twist the question on its head. What is the goal here? What are you trying to achieve by having something else in that box?
Simon.
Lets twist the question on its head. What is the goal here? What are you trying to achieve by having something else in that box?
Simon.
ASKER
Hi All,
Thank you so much for all of your helps. Here is our goal.
We have a group of users that will need to access the exchange via other domains. Their DNS server can see our "exchange.domain.com" but not "exchange.domain.local. Therefore, if we can somehow make it Exchange Server Settings: looks at "exchange.domain.com" or "IP address" in stead of "exchange.domail.local" FQDN, then we don't need to configure new DNS for each other domains with "exchange.domain.local." This will save us alots of troubles.
I have tried to remove "exchange.domain.local" from our local ADs (DC/GC) DNS and configure it at exchange.domain.com only. Local AD's DNS has domail.com setup as secondary but this did not work.
I think if we manually added it to the host file it will work, but it'll be too much troubles.
Is there anyway, we can make it this to work??
Again, I want to thank you all for your generous helps.
Thank you so much for all of your helps. Here is our goal.
We have a group of users that will need to access the exchange via other domains. Their DNS server can see our "exchange.domain.com" but not "exchange.domain.local. Therefore, if we can somehow make it Exchange Server Settings: looks at "exchange.domain.com" or "IP address" in stead of "exchange.domail.local" FQDN, then we don't need to configure new DNS for each other domains with "exchange.domain.local." This will save us alots of troubles.
I have tried to remove "exchange.domain.local" from our local ADs (DC/GC) DNS and configure it at exchange.domain.com only. Local AD's DNS has domail.com setup as secondary but this did not work.
I think if we manually added it to the host file it will work, but it'll be too much troubles.
Is there anyway, we can make it this to work??
Again, I want to thank you all for your generous helps.
Manually create a zone file in the other domain's dns for domain.local and then add a CNAME (alias) for exchange.domain.local pointing to exchange.domain.com or an A record (host) for mail.domain.local pointing to the IP of the mail server.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I guess we have to manually add the DNS for all other domains.
I have splited points for everyone. Thank you so much for all of your help.
I have splited points for everyone. Thank you so much for all of your help.
Nothing to see here.