[Mailman-Users] Server Migration

Dennis Putnam dap1 at bellsouth.net
Wed Feb 12 08:58:59 EST 2020


Hi Robert,

Thanks for the reply. I have no access to DNS which is why the old
server needs to be shutdown and the new server renamed the same as the
old server and the IP address changed to match. I have root access to
the mailman server. I'll reply to Mark's message with more detail.

On 2/11/2020 3:50 PM, Robert Heller wrote:
> At Tue, 11 Feb 2020 14:42:15 -0500 Dennis Putnam <dap1 at bellsouth.net> wrote:
>
>>
>>
>> Content-Language: en-US
>>
>> I've been reading up on migrating to a new server but I'm not sure I am
>> reading the right instructions. It seems that copying the lists to the
>> new server is one thing but it appears that the end result means the
>> users will have to use a new list server. That is, if users were
>> emailing listname at oldserver.domain.com they will now have to email
>> listname at newserver.domain.com. That is not what I want. After migrating
>> to the new server I want users to still email
>> listname at oldserver.domain.com. I expect to simply rename the new server
>> to the old hostname and change its IP address. Can someone point me to
>> some documentation that does that type migration? TIA.
> You don't "name" (or rename) the server.  You update the DNS server to use the 
> new server's IP address for the old hostname.  How you update the DNS server 
> greatly depends on exactly what sort of access you have to the DNS server.
>
> It also depends on what level of access you have to the server(s).  Are these 
> VPSs? Physical server boxes?  Are you just swapping physical hardware?  If you 
> are swapping *physical hardware*, then you could, once the files are copied 
> and everything is working (eg you have tested things as newserver.domain.com), 
> you could shutdown the original oldserver.domain.com, and then reconfigure 
> newserver.domain.com's IP address to be what oldserver.domain.com was.  In 
> that case, there is no need to mess with the DNS server. (You might need to 
> mess with a DHCP server, depending on how IP addresses are set up.)
>
> In order to point you in the right direction, you need to tell us more...
>
>> Content-Description: OpenPGP digital signature
>>
>> -----BEGIN PGP SIGNATURE-----
>>
>> iF0EARECAB0WIQTebsbo9TQsIuOkbg/9+JZipna1VAUCXkMDmAAKCRD9+JZipna1
>> VGajAKDxxI26C50i0+eKII1m8vtNZeuBowCdEXAqTWrPLMx742cnqMIdBBfKYc4=
>> =5/6h
>> -----END PGP SIGNATURE-----
>>
>> MIME-Version: 1.0
>>
>> ------------------------------------------------------
>> Mailman-Users mailing list Mailman-Users at python.org
>> https://mail.python.org/mailman/listinfo/mailman-users
>> Mailman FAQ: http://wiki.list.org/x/AgA3
>> Security Policy: http://wiki.list.org/x/QIA9
>> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
>> Unsubscribe: https://mail.python.org/mailman/options/mailman-users/heller%40deepsoft.com
>>
>>                                                                     


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/mailman-users/attachments/20200212/aced7a6a/attachment-0001.sig>


More information about the Mailman-Users mailing list