[Last Call] Learn how to a build a cloud-first strategyRegister Now

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

Removing a domain name from Exchange server

We have an Exchange 2003 email server running three email domain names, eg:

domain1.com
domain2.com
domain3.com

We have moved domain3.com to a new server (external/internet based now). However, when users on domain1.com or domain2.com try to send email to domain3.com, it bounced back saying the recipient is unknown, eg:

Your message did not reach some or all of the intended recipients.
Subject:  
Sent: 23/03/2006 07:59
The following recipient(s) could not be reached:
  user1@domain1.com on 23/03/2006 07:59
  The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the correct address.
  <mail.encams.local #5.1.1>

The email sent to domain3.com is not leaving the exchange server (we are monitoring at gateway level). How can we remove all traces of the domain3.com from our current exchange server, therefore forcing the email "out" of the gateway?

On Exchange 5.5, to remove a domain name, you simply go to site > configuration > site addressing > and remove the email domain name from there.

How would I remove domain3.com from my Exchange 2003 server?

Urgent, hence 500 points.

0
Encams
Asked:
Encams
  • 17
  • 9
  • 9
2 Solutions
 
rakeshmiglaniCommented:
how did you move domain3.com to a new server?
is the new server part of the same exchange ORG and Admin group?
0
 
EncamsAuthor Commented:
Hi.

domain3.com is now not on our lan, our building, our network or anything, it is a completely separate entity which we have created externally (on the internet) and is hosted externally.

We "simply" need to remove traces of domain3.com from our existing AD/Exchange to enable email addressed to domain3.com to go "out" to the Internet, instead of it looking "locally" for it.

0
 
rakeshmiglaniCommented:
have you checked your recipient policies?
is the domain3.com email address configured there?
0
Configuration Guide and Best Practices

Read the guide to learn how to orchestrate Data ONTAP, create application-consistent backups and enable fast recovery from NetApp storage snapshots. Version 9.5 also contains performance and scalability enhancements to meet the needs of the largest enterprise environments.

 
EncamsAuthor Commented:
Hi.

We edited the recipient policy for domain3.com and simply changed the email address to domain3.com.old

Will this suffice?
0
 
rakeshmiglaniCommented:
if you are not using it then why not remove it from the policies.
0
 
EncamsAuthor Commented:
What would happen if I were to delete that recipient policy completely?

It is currently # 1 in the policies list.

Would anything else be affected?
0
 
rakeshmiglaniCommented:
how many policies do you have?
are the other domain names also configured in this policy or do you have seperate policies for the other 2 domains
0
 
EncamsAuthor Commented:
Hi.

Separate policies for each domain name, so only domain3.com is in the top one.

Safe to delete then!
0
 
EncamsAuthor Commented:
Hi.

Policy deleted, tried sending an email to domain3.com and still get the same error:

Your message did not reach some or all of the intended recipients.
Subject: test to dom3
Sent: 23/03/2006 09:53
The following recipient(s) could not be reached:
  test.user@domain3.com on 23/03/2006 09:53
  The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the correct address.
  <mail.encams.local #5.1.1>


I have re-applied the remaining policies.
0
 
rakeshmiglaniCommented:
is this a mix mode setup (exchange 5.5 and exchange 200x)? or just pure exchange 200x

lower the priority of this policy so that the other two (domain1 and domain2) are set as priority 1 and 2 or priority 2 and 1.

make sure that you have not configured any thing else in the policy for domain3.com like FAX addresses or any custom address.

the delete the domain3.com policy

wait for replication or restart the exchange services
0
 
EncamsAuthor Commented:
Hi.

Tricky to restart services during the day. Can I force replication now?

(no mixed mode by the way)

0
 
rakeshmiglaniCommented:
how many servers?

you can force the AD replication.
0
 
EncamsAuthor Commented:
Just the one email server.

How can i force a replication please?
0
 
rakeshmiglaniCommented:
open AD sites and Services.
you will see your DC/GCs listed there.
click on NTDS Settings and on the right side you would see the replication connector
Right click on it and select replicate now

this would replicate the AD information between the Dcs/GCs

but the replication in exchange takes time as some information is cached in exchange configuration and metabase. for the exchagne part give it some time, like 30 minutes or so
0
 
EncamsAuthor Commented:
Thanks for your help, but alas, still no luck.

No change at all, same error.  It is as if it still has a record or a trace of domain3.com in there somewhere.

Anything else I can try or look for?


0
 
rakeshmiglaniCommented:
i would suggest a restart of all the exchange services to flush the old information.

you can also check the settings in your existing policies whether the domain3.com smtp address is present there

also has any configuration been done in the smtp virtual server settings or any smtp connector created or modified
0
 
rakeshmiglaniCommented:
How to configure the SMTP connector in Exchange 200x
http://support.microsoft.com/kb/265293/en-us

When to create SMTP connectors in Exchange 2000 and later
http://support.microsoft.com/kb/294736/en-us

How to install and to configure SMTP Connectors in Exchange 2000 Server
http://support.microsoft.com/kb/314961/en-us
0
 
LeeDerbyshireCommented:
Do you have internal MX records for domain3.com in DNS ?

Try this from a CMD box on your Exchange server:


ntslookup
set type=mx
domain3.com


It should show you where it wants to send the mail.
0
 
EncamsAuthor Commented:
Hi Lee.

NS Lookup resolves correctly to the external ip of domain3.com

Could Exchange be caching dns lookups?

0
 
LeeDerbyshireCommented:
If it was, you would see it in NSLookup.  Maybe the address doesn't exist in domain3.com , then.  How sure are you that it does.  I know you said the mail doesn't leave the server, but if the receiving server can't match the name when your server is negotiating with it, then the email wouldn't go anywhere.  Try a telnet session with the remote server.

telnet xxx.xxx.xxx.xxx 25
helo
mail from:you@yourdomain.com
rcpt to:address@domain3.com
data
hello
.
quit

see what happens.
0
 
EncamsAuthor Commented:
Hi again.

Our exchange server uses a local smarthost, it does not have direct internet access.

I can telnet out on port 25 to the smarthost and send a telnet email with no problems.

This is how I know the domain3.com email is not leaving the server, as we are not seeing an incomming connection on the smarthost server from the Exchange server when trying to email domain3.com

The plot thickens!
0
 
LeeDerbyshireCommented:
Is the smarthost entered into your Default Virtual Server, or an SMTP connector?  If it's an SMTP connector, you will need to add domain3.com to its list of namespaces, unless it already has * in the list.
0
 
EncamsAuthor Commented:
Hi.

If I goto the properties of the Default SMTP Connector, in the General tab, the smarthost is listed in there. Under the Address Space tab of the same properties window, I simply have a * entry for SMTP.
0
 
LeeDerbyshireCommented:
OKay, so everything's going through that.  I think the next thing I would try is to do an NSLOOKUP from the smarthost, to see where that thinks mail for domain3.com should be going.
0
 
EncamsAuthor Commented:
Hi.

The smarthost mx record lookup still looks to the internet on the correct ip, but as above, the smarthost is not seeing/getting a connection from the exchange server when sending email to domain3.com

It's as if the email refuses to leave the local exchange server as there are traces or something still prompting the exchange server to think that it still manages email for domain3.com !?

0
 
LeeDerbyshireCommented:
So, you definitely have no recipient policies containing this domain? Is the Default SMTP Virtual Server configured to use external DNS servers (Delivery/Advanced)?

Do you have Message Tracking enabled?
0
 
EncamsAuthor Commented:
Definately no recip pols left containing domain3.com

Default SMTP Virtual Server uses the same smarthost, external dns servers part is empty. Worth me adding an internet-based dns server in there?

Bear in mind still, I don't think the email is getting this far (to the point of external/smtp delivery) ?

Alas, we have no message tracking in place.
0
 
EncamsAuthor Commented:
Pulling (whats left) of my hair out on this one now.

Can I create a virtual "something" so if Exchange sees an email address to domain3.com it knows to send it out via the smarthost address?

0
 
LeeDerbyshireCommented:
I wouldn't add an external DNS server if the name is resolving correctly.  On the other hand, it would do no harm to try it for a few minutes, I guess.  I was just wondering if there was something already in there, it may be best to take it out, that's all.  I don't think you need the smarthost configured on the VS if it is also on the Connector, but this wouldn't give you a problem for just one domain.

I would try turning in message tracking, then you can see what happens to the message as it passes through various parts of the messaging path.
0
 
EncamsAuthor Commented:
Ok, message tracking on.

I get:

store drive: message submitted from store
message submitted to advanced queing
message submitted to categorizer
message categorized and queued for routing
non-delivered report (ndr) generated


Can I break that down further still?
0
 
LeeDerbyshireCommented:
No.  But that is exactly what you'd get for a badly-addressed internal mail.  So, it is definitely not leaving the server.

Is there anything interesting in the Event Logs on the Exchange server?
0
 
EncamsAuthor Commented:
Not a thing, eventwvr all looking healthy and normal, no traces of anything out of place.

Any workarounds or anything?
0
 
LeeDerbyshireCommented:
I think it's time for a restart of the Exchange services, I'm afraid.  You might try adding domain3.com back into you Default Recipient Policy, and then removing it again, in case it got confused last time you removed it, or something.  But I wouldn't expect anything miraculous to happen.

You have no trace of domain3.com in Active Directory Domains and Trusts?  Or in DNS Manager?
0
 
EncamsAuthor Commented:
Thanks for your help Lee, will reboot at 7AM (empty office!) and keep you posted.
0
 
LeeDerbyshireCommented:
Did the reboot fix it?  Was it as simple as that?
0

Featured Post

Creating Active Directory Users from a Text File

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.

  • 17
  • 9
  • 9
Tackle projects and never again get stuck behind a technical roadblock.
Join Now