Managing Active Directory does not always have to be complicated. If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why
Solved
Exchange Server 2003 Name Issue - Domain.local
Posted on 2006-06-14
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.
3
2-
2
- +1
8 Comments
Seems there is nothing wrong here!!!
By default when you configure the user's profile and do check name it will take the exchange server local FQDN name itself.
As while configuring profile it queries to the AD(DC/GC) through local DNS
i.e exchange.domain.local
It will never look for exchange.domain.com.
Regards,
Prasad
By default when you configure the user's profile and do check name it will take the exchange server local FQDN name itself.
As while configuring profile it queries to the AD(DC/GC) through local DNS
i.e exchange.domain.local
It will never look for exchange.domain.com.
Regards,
Prasad
That is exactly what is supposed to happen... it changes it to the FQDN of the ex box.
Nothing to see here.
Nothing to see here.
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.
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.
Alternatively you can put the IP of the DNS server for domain.local as a forwarder on the other domains that you want to have access.
The name will always change.
That is how Exchange/Outlook is designed. You can put what you like in to the hosts file, the name will always change to the machine's real name.
Are you attempting to go across the Internet?
You sound like an ideal candidate for RPC over HTTPS. This will allow you to use a public name for Internet traffic.
Simon.
That is how Exchange/Outlook is designed. You can put what you like in to the hosts file, the name will always change to the machine's real name.
Are you attempting to go across the Internet?
You sound like an ideal candidate for RPC over HTTPS. This will allow you to use a public name for Internet traffic.
Simon.
Featured Post
If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Fix RPC Server is unavailable Error in Exchange 2013, 2010, 2007, and 2003 Server. Different reason can such as network connectivity issue, name resolution issue, firewall, registry corruption that lead to RPC Server Unavailable error.
How to Import Outlook PST file to Exchange Server Mailbox without Powershell and Exchange Admin Center. Use SysTools Exchange Import Tool to Move PST file in Exchange 2016 / 13 / 10/ 07 Server Mailbox including Contacts, Calendar, Task and journal d…
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment.
The video tutorial explains the basics of the Exchange server Database Availability grou…
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online.
The email signature template has been downloaded from:
www.mail-signatures…
Suggested Courses
Course of the Month4 days, 15 hours left to enroll
579 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.