Mailing List SIMS@mail.stalker.com Message #15428
From: Todd Reed <Todd.Reed@pphsso.org>
Subject: Re: SIMS dual domains
Date: Wed, 07 Feb 2007 10:45:18 -0800
To: SIMS Discussions <SIMS@mail.stalker.com>
Great, thanks for the replies. That about covers it for me.

Todd


On 2/7/07 9:45 AM, "Christopher Bort" <cbort@globalhomes.com> wrote:

> On 02/07/07 at 06:28, Todd Reed wrote:
>
>> Hi all,
>>
>> Still running SIMS here despite all rumors to the contrary.
>>
>> I need to run dual domains on SIMS as the organization is moving to a
>> new domain name. We want mail sent to user@olddomain.com or
>> user@newdomain.com to both go to the same user mailbox.
>>
>> My checklist is as follows:
>>
>> Turn down TTL's on existing domain.
>
> Why? If you follow your plan outlined below, the existing MX,
> mail.olddomain.com, will continue to point to your mail server without
> interruption, no? Whether a sending MTA uses a the old A record from a
> cache or gets the new CNAME, it will still resolve to the IP address of
> your SIMS machine. Unless you're changing the IP address of your server,
> but it doesn't sound like that's the case.
>
>> Establish new domain with A, and MX records pointing to SIMS.
>>
>> Give SIMS it's new domain name: mail.newdomain.com
>> Set up a routing entry: *@olddomain.com=newdomain.com
>
> That should be:
>
> <*@olddomain.com> = *@newdomain.com
>
> However, if all user names are the same for both domains, you can simplify
> that to:
>
> olddomain.com = newdomain.com
>
> Put this at the top of your router, above any entries that route individual
> addresses within the domains.
>
>> Set up CNAME on old domain name record:
>> mail.olddomain.com CNAME mail.newdomain.com
>> Remove A record for mail.olddomain.com
>> MX record on old domain points to mail.newdomain.com
>
> That's all optional and entirely up to you. The record for
> mail.olddomain.com can remain as an A, especially if you're reasonably
> confident that your server will keep the same IP address for a while.
> CNAMEs can get messy, so I usually try to avoid them when an A record will
> do the job.
>
> More to the point would be to simply change the MX record for olddomain.com
> to point to mail.newdomain.com (an MX does not have to be in the same
> domain):
>
> olddomain.com   MX   10   mail.newdomain.com
>
> Again, you don't need to fiddle with TTLs here because mail.olddomain.com
> and mail.newdomain.com will point to the same IP address. If you make
> mail.newdomain.com the MX for olddomain.com, then you can remove the
> A|CNAME for mail.olddomain.com entirely after its TTL expires.
>






Subscribe (FEED) Subscribe (DIGEST) Subscribe (INDEX) Unsubscribe Mail to Listmaster