Find the answer to your Linux question:
Results 1 to 5 of 5
Hey all, I need ideas. In an internal network, I need to configure a secondary virtual mail server for high availability. Problem is, DNS is not used, so a bunch ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Sep 2011
    Posts
    2

    Mail servers sharing an ip


    Hey all, I need ideas.

    In an internal network, I need to configure a secondary virtual mail server for high availability. Problem is, DNS is not used, so a bunch of clients are configured to use the current virtualized mail server by IP address. Thanks for your ideas!

  2. #2
    Trusted Penguin Irithori's Avatar
    Join Date
    May 2009
    Location
    Munich
    Posts
    3,444
    There is a way of moving an IP between hosts, but the scenario you describe calls for a better and easier solution:
    - Introduce DNS
    - Communicate that
    - Set a deadline for the clients.

    Good mailservice cannot and should not be done without DNS.
    For a start, look at the Priority argument of the MX resource record.
    You must always face the curtain with a bow.

  3. #3
    Just Joined!
    Join Date
    May 2010
    Posts
    30

    hmmm

    Well, I may be just talking nonsense, but I have a simple solution.
    I came up with this while setting up a minecraft server.

    Ok, since email NORMALLY runs on these ports, on any given IP address (weather it be an internal 192.* or an external)

    POP3 - port 110
    IMAP - port 143
    SMTP - port 25
    HTTP - port 80
    Secure SMTP (SSMTP) - port 465
    Secure IMAP (IMAP4-SSL) - port 585
    IMAP4 over SSL (IMAPS) - port 993
    Secure POP3 (SSL-POP) - port 995

    Now, theoretically, you should be able to run multiple instances by just changing the port of the mail server. So, if your normal email server is on say 192.168.100.100:110 (pop3) you could also run an additional server on 192.168.100.100:120, you of course would need separate installs for each server. You would just have to change what port the email software the client is attempting to connect at.

  4. $spacer_open
    $spacer_close
  5. #4
    Linux Enthusiast Mudgen's Avatar
    Join Date
    Feb 2007
    Location
    Virginia
    Posts
    664
    If it's just an smtp relay, it's not too tough to have each host with individual ip on eth0:1 and switchable ip on eth0:2, which is not started at boot (ONBOOT=NO in ifcfg-eth0:2). Each starts checking the switchable ip at boot and ongoing, and if not pingable, brings up its eth0:2. If it's a full blown mail server, delivering to boxes and serving pop/imap clients, you also need clustered storage and replication of the client credentials.

    But there's a lot of potential for trainwrecks, ways for both servers to be trying to use the ip at once. I've tried it (relay only) and it worked just well enough to drive me half nuts. Irithori gives good advice, as usual.

  6. #5
    Just Joined!
    Join Date
    Sep 2011
    Posts
    2

    Thanks

    Irithori, I know, and wish it were that simple. Unfortunately, DNS is performed inside a closed system.

    Mudgen, a coworker described that case to me, and I'll most likely give it a shot. I'll probably also go mad.

    Thanks for the suggestions!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •