Managing Clients Across Multiple Servers

Overview

When your reseller package requires splitting clients between multiple MXroute servers (safari.mxrouting.net, lucy.mxrouting.net, everest.mxrouting.net), proper DNS configuration becomes critical for seamless client experience. This guide provides the recommended approach using numbered subdomains.

Why Split Server Management Matters

• Capacity Management: Server resources may require distribution
• Technical Requirements: Some configurations work better on specific servers
• Service Continuity: Proper DNS setup ensures clients don't experience service interruptions

The Problem with Default DirectAdmin SSL Subdomains

DirectAdmin's default SSL configuration creates subdomains like:

• mail.yourdomain.com
• webmail.yourdomain.com

These work well when all clients are on the same server, but create confusion and configuration conflicts when clients are split across multiple servers.

Recommended Solution: Numbered Subdomains

Instead of generic subdomains, use server-specific numbered subdomains. Note: You're free to use any naming scheme you prefer - this is simply our recommended approach for clarity and organization.

Subdomain Structure

• mx01.yourdomain.com - Points to your primary server
• mx02.yourdomain.com - Points to your secondary server
• mx03.yourdomain.com - Points to tertiary server (if needed)

Benefits of This Approach

1. Clear Server Identification: Easy to track which clients are on which server
2. Scalability: Can easily add mx04, mx05, etc. as you grow
3. Professional Appearance: Maintains consistent branding
4. Reduced Confusion: No conflicts between generic "mail" subdomains

Key Concepts for Multi-Package Resellers

One Subdomain Per Server (Not Per Package)

Important: If you have multiple reseller packages on the same MXroute server, you only need ONE numbered subdomain for that entire server.

Example Scenario:

• Package A (75GB) on safari.mxrouting.net
• Package B (150GB) on safari.mxrouting.net
• Package C (200GB) on lucy.mxrouting.net

Correct Setup:

• mx01.yourdomain.com → safari.mxrouting.net (covers both Package A AND Package B)
• mx02.yourdomain.com → lucy.mxrouting.net (covers Package C)

Why This Works: All packages on the same physical server share the same SSL infrastructure. One subdomain certificate covers everything on that server.

DNS Configuration Steps

Step 1: Create CNAME Records

ALWAYS use CNAME records for your numbered subdomains pointing to the appropriate MXroute server:

mx01.yourdomain.com    CNAME    safari.mxrouting.net
mx02.yourdomain.com    CNAME    lucy.mxrouting.net
mx03.yourdomain.com    CNAME    everest.mxrouting.net

Step 2: Configure SSL Certificates

In DirectAdmin, configure SSL certificates for your numbered subdomains on each specific server only:

1. On safari.mxrouting.net: Add SSL certificate for mx01.yourdomain.com ONLY
2. On lucy.mxrouting.net: Add SSL certificate for mx02.yourdomain.com ONLY
3. On everest.mxrouting.net: Add SSL certificate for mx03.yourdomain.com ONLY

Important: Only create the SSL certificate on the server that subdomain points to. Do not create mx01 SSL on lucy server or mx02 SSL on safari server.

Step 3: Server Capacity Management Strategy

Critical: Proper capacity planning prevents the need for client migrations later.

Recommended Starting Approach

1. Start with a 150GB package: This provides good room for growth while remaining cost-effective
2. Monitor actual usage closely: Track real storage consumption, not just account count
3. Upgrade threshold: When usage reaches 120GB (80% of 150GB), upgrade to 200GB and stop provisioning new clients on that package
4. Start fresh: Begin provisioning new clients on a new package/server

Why Monitor Usage Closely?

Every reseller operates differently:

• Large package resellers (25GB+ per client): Will hit capacity limits faster with fewer clients
• Small package resellers (<10GB per client): Can accommodate many more clients before hitting limits
• Mixed portfolios: Need to track both client count and actual consumption patterns

This is why you must monitor your actual usage - there's no one-size-fits-all rule.

Available Package Sizes

MXroute offers reseller packages in 75GB, 150GB, and 200GB sizes.

Example Growth Pattern

• mx01 (150GB package): Provision clients until 120GB actual usage reached
• Upgrade mx01 to 200GB, stop adding new clients to mx01
• mx02 (new 150GB package): Start provisioning new clients here
• mx03: Add when mx02 reaches 120GB usage

What NOT to Do

❌ Don't wait until a server is completely full before planning expansion
❌ Don't ignore the difference between allocated space and actual usage
❌ Don't assume your client usage patterns match other resellers
❌ Don't create multiple mx## subdomains for packages on the same server - one subdomain per physical server is sufficient

Client Configuration Instructions

Email Client Setup (IMAP/SMTP)

Provide clients with server-specific settings:

For clients on mx01:

• IMAP Server: mx01.yourdomain.com
• SMTP Server: mx01.yourdomain.com
• Webmail URL: https://mx01.yourdomain.com/webmail

For clients on mx02:

• IMAP Server: mx02.yourdomain.com
• SMTP Server: mx02.yourdomain.com
• Webmail URL: https://mx02.yourdomain.com/webmail

Standard Settings (Same for All)

• IMAP Port: 993 (SSL/TLS)
• SMTP Port: 587 (STARTTLS) or 465 (SSL/TLS)
• Authentication: Required for both IMAP and SMTP

Documentation and Client Communication

Create Client-Specific Welcome Emails

Template example:

Welcome to [Your Company] Email Services!

Your email server details:
- Server: mx01.yourdomain.com
- Webmail Access: https://mx01.yourdomain.com/webmail
- Username: [client's email]
- Password: [provided separately]

For email client setup, use:
- Incoming (IMAP): mx01.yourdomain.com, Port 993, SSL
- Outgoing (SMTP): mx01.yourdomain.com, Port 587, STARTTLS

Maintain Server Assignment Records

Keep a spreadsheet or database tracking:

• Client domain/email
• Assigned server (mx01, mx02, mx03)
• Setup date
• Any special configurations

Conclusion

Using numbered subdomains (mx01, mx02, mx03) provides a clean, scalable solution for managing clients across multiple MXroute servers. This approach eliminates confusion, maintains professional appearance, and allows for easy expansion as your reseller business grows.

Remember: Proper DNS management is crucial for client satisfaction and your business reputation. When in doubt, test configurations thoroughly before deploying to live client environments.