Skip to main content

Primary Domain

The primary domain allows you to use a different domain from your Mumara installation domain for publicly visible actions, such as tracking links and CNAME redirection for tracking domains. This helps keep your installation domain private while using an alternative domain for system features that are publicly accessible.

Navigate to Settings → Primary Domain to configure your domain.

Why Use a Primary Domain?​

By default, tracking links and other publicly visible URLs use your Mumara installation domain. Setting a primary domain lets you:

  • Keep your installation private - Your actual server URL isn't exposed in email tracking links
  • Use a branded domain - Tracking links show your brand domain instead of a technical URL
  • Simplify CNAME setup - Tracking domains can point to your primary domain
  • Maintain consistency - All public-facing URLs use the same domain

You can still choose to use your installation domain as the primary domain if privacy separation isn't needed.

Configure Primary Domain​

Current Domain​

The page displays your currently configured primary domain with status indicators:

ElementDescription
Primary DomainThe domain currently set with status indicator
Status indicatorQuestion mark (?) = pending confirmation, Green checkmark = validated
Edit buttonClick to change the primary domain
Recheck DNS RecordRe-verify DNS after initial confirmation

Setting or Changing the Domain​

  1. Click the Edit button next to the current domain
  2. Enter your new primary domain (e.g., tracking.yourdomain.com)
  3. Save the changes
  4. The page displays required DNS records with a Confirm button
  5. Configure your web server to accept the new domain (see below)
  6. Add the DNS record at your DNS provider
  7. Wait for DNS propagation (typically 15-60 minutes)
  8. Click Confirm to validate
Wait Before Confirming

Do not click Confirm immediately. First add the DNS record at your DNS provider, then wait for propagation before clicking Confirm.

If you click Confirm before DNS is properly configured, the failed lookup result gets cached. This can delay validation even after you add the correct DNS record. Wait until you're confident the DNS is set up, then confirm.

This same principle applies to DNS records on the Sending Domain page.

After Confirmation​

Once you click Confirm, Mumara validates the DNS record:

  • Success: Green checkmark appears with message "Primary domain has been validated successfully"
  • Failure: Question mark remains, indicating DNS issue

After the initial confirmation, only the Recheck DNS Record button is available to re-validate if needed.

DNS Configuration​

Add an "A Record"​

After setting your primary domain, the page displays the required DNS record. Login to the DNS zone of your domain and add the record shown.

ColumnDescription
HostThe full domain name (your primary domain)
TypeA
ValueYour server's IP address

Example DNS Record​

Host: tracking.yourdomain.com
Type: A
Value: 192.168.25.5

Where to Add DNS Records​

DNS records are managed where your domain is registered or where nameservers point:

  • Domain registrar - GoDaddy, Namecheap, Google Domains, etc.
  • DNS provider - Cloudflare, Route 53, DNS Made Easy, etc.
  • Hosting control panel - cPanel, Plesk, DirectAdmin, etc.

DNS Propagation​

After adding the DNS record:

  • Changes can take up to 48 hours to propagate globally
  • Most changes propagate within 1-4 hours
  • Use Recheck DNS Record to verify when propagation is complete

Web Server Configuration​

Before the primary domain will work, your web server must be configured to accept requests for the new domain and serve Mumara from the correct directory.

Apache Virtual Host​

Add a virtual host entry for your primary domain:

<VirtualHost *:80>
    ServerName tracking.yourdomain.com
    DocumentRoot /path/to/mumara/public

    <Directory /path/to/mumara/public>
        AllowOverride All
        Require all granted
    </Directory>
</VirtualHost>

For HTTPS (recommended):

<VirtualHost *:443>
    ServerName tracking.yourdomain.com
    DocumentRoot /path/to/mumara/public

    SSLEngine on
    SSLCertificateFile /path/to/certificate.crt
    SSLCertificateKeyFile /path/to/private.key

    <Directory /path/to/mumara/public>
        AllowOverride All
        Require all granted
    </Directory>
</VirtualHost>

After adding, restart Apache:

sudo systemctl restart apache2

Nginx Server Block​

Add a server block for your primary domain:

server {
    listen 80;
    server_name tracking.yourdomain.com;
    root /path/to/mumara/public;
    index index.php;

    location / {
        try_files $uri $uri/ /index.php?$query_string;
    }

    location ~ \.php$ {
        fastcgi_pass unix:/var/run/php/php8.2-fpm.sock;
        fastcgi_param SCRIPT_FILENAME $realpath_root$fastcgi_script_name;
        include fastcgi_params;
    }
}

For HTTPS, add SSL directives and listen on port 443.

After adding, restart Nginx:

sudo systemctl restart nginx

Control Panel Users​

If using a hosting control panel (cPanel, Plesk, DirectAdmin):

  1. Add the primary domain as an addon domain or alias
  2. Point it to the same document root as your Mumara installation
  3. The control panel handles virtual host configuration automatically
tip

Configure the web server before adding the DNS record. This ensures when DNS resolves, the server is ready to respond correctly.

Verification​

Status Indicators​

IndicatorMeaning
? (Question mark)Domain added but not yet confirmed/validated
Green checkmarkDNS validated successfully

Using Recheck DNS Record​

After the initial confirmation, use Recheck DNS Record to re-validate DNS if:

  • You made changes to your DNS records
  • The initial confirmation failed and you've now fixed DNS
  • Your server IP changed and you updated the A record

Troubleshooting Verification​

If verification fails:

  1. Confirm you added the A record to the correct domain zone
  2. Verify the IP address matches your server exactly
  3. Wait for DNS propagation (can take up to a few hours)
  4. Check for typos in the hostname
  5. Ensure no conflicting CNAME record on the same hostname
  6. If you confirmed too early, wait for the cache to expire and use Recheck DNS Record

Usage After Configuration​

Once your primary domain is configured and verified:

Email tracking links (opens, clicks) will use your primary domain:

Before: https://your-installation.com/track/click/abc123
After:  https://tracking.yourdomain.com/track/click/abc123

CNAME Tracking Domains​

When setting up tracking domains for lists, you can point CNAME records to your primary domain instead of your installation domain.

Webforms and Public Pages​

Subscription forms and other public pages can use the primary domain for a consistent branded experience.

Best Practices​

  • Use a subdomain - Use something like tracking., mail., or links. rather than your root domain
  • Keep it simple - Short, memorable subdomains work best
  • Match your brand - Use a domain that aligns with your organization's identity
  • SSL coverage - Ensure SSL certificates cover your primary domain for HTTPS
  • Test thoroughly - Send test emails and verify tracking links work correctly

Troubleshooting​

DNS Record Not Found​

Possible causes:

  • Record not yet added
  • DNS propagation incomplete
  • Record added to wrong zone

Solutions:

  • Verify record exists in your DNS provider
  • Wait 1-4 hours for propagation
  • Double-check you're editing the correct domain's DNS

IP Address Mismatch​

Possible causes:

  • A record points to wrong IP
  • Server IP changed
  • Using a proxy/CDN that changes the IP

Solutions:

  • Update A record with correct server IP
  • If using Cloudflare or similar, ensure proper configuration

Possible causes:

  • Primary domain not verified
  • Cache not cleared
  • List-level tracking domain overriding

Solutions:

  • Verify primary domain status shows green checkmark
  • Clear application cache
  • Check individual list settings for tracking domain overrides

Next Steps​

Last updated on