Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 413
  • Last Modified:

Exchange Server 2007 / Domain Name questions

We are running Windows Server 2003 and Exchange 2007.

Our AD domain got named (somewhat improperly) at first and we went ahead and used that name. No harm, except possibly now...

Our internal mail server maps to a name like exchange.domainname.com

It is completely accessible from inside the network. I just tried accessing it from outside with no luck. I then tried pinging the mail server by that name, then realized no DNS record exists to map that name to our external IP.

Here is the problem...

Our actual, registered domain name would be domainnameinc.com, not domainname.com

Since our internal domain name differs from the external, and someone has already registered our internal domain name, what can I do about creating a record that points our Exchange server to our outside IP?

Are we talking about having to rename the domain?
0
cwelectric
Asked:
cwelectric
  • 7
  • 5
1 Solution
 
gupnitCommented:
Hi,
Your options are:
  • Buy out the other domain, that someone else has taken over.
  • If you are OK with domainnameinc.com, then just make Exchange Authoritative for that domain and create necessary MX records, and you will  start receving mails for that domain. Internal domain name ideally should be different from external, so it will infact be good for you. For auth: http://support.microsoft.com/kb/268838
Let me know
Thanks
Nitin
0
 
cwelectricAuthor Commented:
I have made Exchange authoritative for the domain in question.

The problem is, the actual exchange server name when plugged into Outlook. It works internally, but externally there is no DNS record pointing to that name.

Am I being confusing...?
0
 
cwelectricAuthor Commented:
Meaning that I can get Exchange to accept mail for the domain, that is not the issue.

The issue is actually being able to use Exchange via Outlook, outside of the LAN where a DNS record must exist to find the Exchange server name. The name that someone else has registered.

And that domain name doesn't expire until like July...I've checked that route...
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
gupnitCommented:
Hi,
Exchange server name is never a concern. Make sure that the domainnameinc.com mailaddress is  primary for the users and it would solve all problems. Internally change the DNS records too and point domainnameinc.com to exchange server.
Am I missing sth still here
Thanks
Nitin
0
 
cwelectricAuthor Commented:
I'm not sure, maybe I'm not explaining myself all that well.

"domainnameinc.com" is set as the primary SMTP address for all users. I have also tested mail flow internally and externally and confirmed it to be working. The MX record that points to those domain names is not the one I'm trying to resolve externally. All of that works.

I am concerned with an Outlook client for this Exchange server that is configured with a server name of "exchange.xxx.domainname.com".

That name works internally to connect to the Exchange server, authenticate users, send/receive mail, etc.

Externally, that name will not even connect to the Exchange server. I also cannot resolve that name from outside the internal network via ping.

Do I need to...

A) Rename the Exchange server internally to a name the outside clients can connect to? If so, how do I do that?
B) Create a record outside to point to this internal name? If so, how do I do that, as I do not own the internal domain name?
C) Something else I am missing? Is there another way to get external users connecting to Exchange via Outlook?

0
 
gupnitCommented:
Hi -
Sometimes, difference of communication styles do play role. You will have to be patient with me :-)
Outlook clients are connecting to Exchange server via its FQDN as per AD Domain. So you AD domain is xxx.domainname.com that is internal to your setup. To be able to connect to your Exchange server from external networkplease setup a A record that will point to Exchange server Public IP, for the domainnameinc.com domain
 Let me know
Thanks
Nitin
0
 
cwelectricAuthor Commented:
Apparently there is, using Outlook Anywhere via an Outlook client connecting to the same URL that the web clients use.

http://office.microsoft.com/en-us/outlook/HP101024441033.aspx?pid=CH101395531033
0
 
gupnitCommented:
Hi,
See what is happening in your case is that internal DNS is  using Active Directory Domain based exchange srver name, to avoid that you can use exchange.domainnameinc.com in internal DNS Server and point it to exchange server. That will make sure that internally/externally it is same.
Hope you understood
Thanks
Nitin
0
 
cwelectricAuthor Commented:
So basically, you just mean create a static DNS entry internally that points "exchange.domainnameinc.com" to the Exchange server, and leaving the existing Exchange server name alone?

Then configuring the Outlook client with that newly configured name, which should work internally and externally?
0
 
gupnitCommented:
Yes, if what I have understood about your scenario is correct
0
 
cwelectricAuthor Commented:
I think you have...

When I try to change the name to "exchange.domainnameINC.com within Outlook, after creating the DNS records in AD, the following happens:

The name gets resolved, but it immediately gets placed back to "exchange.xxx.domainname.com". Outlook just changes the name back to the actual server name.

Would you know anything about configuring Outlook to connect to Exchange via Outlook Anywhere?
0
 
cwelectricAuthor Commented:
Purchased SSL certificate and connected Outlook clients externally via Outlook Anywhere.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 7
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now