If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone. 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.
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
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
Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
If you troubleshoot Outlook for clients, you may want to know a bit more about the OST file before doing your next job. IMAP can cause a lot of drama if removed in the accounts without backing up.
A couple of months ago we ran into an issue that necessitated re-creating our Edge Subscriptions. However, when we attempted to execute the command: New-EdgeSubscription -filename C:\NewEdgeSub_01.xml we received an error indicating that the LDAP se…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
This video demonstrates how to sync Microsoft Exchange Public Folders with smartphones using CodeTwo Exchange Sync and Exchange ActiveSync.
To learn more about CodeTwo Exchange Sync and download the free trial, go to: http://www.codetwo.com/excha…
Suggested Courses
Course of the Month11 days, 17 hours left to enroll
730 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.