Email forwarding lets you receive messages at a professional domain address without managing full mailbox accounts. It provides a simple, zero-cost way to route messages from addresses like [email protected] or [email protected] to an existing inbox you already use. This guide explains how forwarding works, how to configure it correctly, and what limitations to expect so that your setup is reliable from the start. Prerequisites: MX Records Required
Email forwarding requires specific DNS records called MX (Mail Exchange) records to function. These records tell other email servers where to deliver messages sent to your domain. Without proper MX records, incoming emails will bounce or fail to deliver.
NameSilo DNS users: If your domain uses NameSilo's nameservers, the system automatically adds the missing MX records.
External DNS users: If your domain points to third-party nameservers (Cloudflare, Route 53, or other DNS providers), you must manually add these MX records in your DNS management panel:
MX Record 1: Priority 10, points to mx4.emailowl.com
MX Record 2: Priority 10, points to mx5.emailowl.com
MX Record 3: Priority 10, points to mx6.emailowl.com
Without these records, email forwarding will not work regardless of how the forwarder is configured. To verify your current DNS setup and manage records, check your DNS configuration before proceeding with forwarding setup. Step-by-Step Email Forwarding Setup
Step 1: Access Your Domain Manager
Log in to your NameSilo account and navigate to the Domain Manager from the left sidebar. This displays all domains registered or managed under your account. Step 2: Open the Domain Console
Click directly on the domain name where you want to set up forwarding. This opens the Domain Console, which contains all management options for that specific domain.
Step 3: Navigate to Email Forwarding
Locate the "Email Forwarding" section in the Domain Console. Click the "Manage" button or the envelope icon to access the forwarding management interface.
Step 4: Create the Email Alias
In the "Alias" or "Prefix" field, enter the part of the email address before the @ symbol. For example:
Catch-all forwarding: You can use an asterisk (*) as the prefix to forward ALL email addresses on your domain to a single destination. This means [email protected], [email protected], and any other address will route to the same inbox. Use this cautiously, as it will forward spam sent to random addresses on your domain. Step 5: Specify Destination Address
Enter the target email address where forwarded messages should arrive. This is typically your personal Gmail, Yahoo, Outlook, or business email account. You can add up to 5 destination addresses for a single forwarder, meaning one incoming email will be copied to multiple inboxes.
Step 6: Submit Configuration
Click the "Submit" button to save the configuration. The system confirms the forwarder was created and displays it in your active forwarders list.
Step 7: Wait for Propagation
Finally, Navigate to the DNS tab on Domain Console and locate the "Apply Email Forwarding Template" button, click it first to add the required MX records. Email forwarding becomes operational within approximately 20 minutes after creation. This propagation period allows DNS changes to spread across email servers globally. Do not test immediately after setup, wait at least 20 minutes before sending test messages.
Troubleshooting Email Forwarding Issues
Emails not arriving at destination
If messages sent to your forwarded address don't appear in your destination inbox, check these factors:
Propagation delay: Wait a full 20-30 minutes after creating the forwarder before troubleshooting. DNS propagation varies by email provider, and some systems take longer to recognize new MX records.
Spam folder: Check the spam or junk folder in your destination email account. Some providers flag forwarded messages as suspicious, especially during the first few days of operation. Mark legitimate forwarded emails as "not spam" to train the filter.
MX records missing: Verify that MX records point to NameSilo's mail servers. Log back into the Domain Console, check the DNS records section, and confirm mx4.emailowl.com, mx5.emailowl.com, and mx6.emailowl.com appear in the MX records list, all with priority 10.
The hairpinning problem: Email forwarding fails when you test by sending a message FROM the destination address TO the forwarded address. For example, if you forward [email protected] to [email protected], then send a test email from [email protected] to [email protected], the message will loop or fail to deliver. Always test forwarding from a third-party email address (a friend's email, a different account you own, or a separate mail service). External DNS issues: If your domain uses external DNS providers instead of NameSilo's nameservers, confirm you added both MX records with correct priorities. Even a single character error in the mail server hostname will break forwarding entirely.
Understanding Email Forwarding Limitations
Email forwarding provides one-way mail routing, not a complete email solution. When you receive messages at your forwarded address, they arrive in your destination inbox showing the original sender's address. This allows you to read and respond to emails normally.
However, replies you send will display your destination email address ([email protected]) as the sender, not your professional forwarded address ([email protected]). Recipients see the personal address in their inbox and reply threads. What you can do: Receive emails at up to 100 professional domain addresses per domain, organize incoming mail using your existing email client, maintain multiple professional addresses (sales@, support@, info@) routing to different team members, use catch-all forwarding to capture all addresses.
What you cannot do: Send emails that appear to originate from the forwarded address, create separate mailboxes with independent login credentials, access forwarded addresses through webmail or mobile apps, exceed 100 forwarders per domain.
For two-way email functionality where you can both receive and send from professional addresses, consider full email hosting solutions. NameSilo's email forwarding works best for simple receiving scenarios, contact forms, and situations where reply addresses don't need to match incoming addresses. Our email services overview compares forwarding versus full mailbox hosting to help determine which solution fits your needs. Frequently Asked Questions
How many email forwarders can I create per domain?
NameSilo allows up to 100 email forwarders per domain. You can create [email protected], [email protected], [email protected], and up to 97 other addresses, each forwarding to different destinations or the same inbox. The catch-all forwarder (*@yourdomain.com) counts as one of the 100 total forwarders. Can I forward one address to multiple destinations?
Yes. Each forwarder supports up to 5 destination addresses. When an email arrives at the forwarded address, copies are sent to all configured destinations simultaneously. This is useful for team scenarios where [email protected] needs to reach three different team members. Does email forwarding work immediately after setup?
No. DNS propagation requires approximately 20 minutes before forwarding becomes operational. Some email providers may take up to an hour to recognize the new MX records. Avoid troubleshooting until at least 30 minutes have passed since configuration.
Why do test emails from my Gmail to my forwarded address fail?
This is the "hairpinning" or "loop detection" issue. When you send from the destination address to the forwarded address, email servers detect a potential loop and block delivery. Always test forwarding using a third-party email address that's different from your destination.
Can I use email forwarding with Cloudflare DNS?
Yes, but you must manually add MX records in Cloudflare's DNS panel. Add three MX records, all with priority 10: mx4.emailowl.com, mx5.emailowl.com, and mx6.emailowl.com.
Does forwarding preserve email attachments?
Yes. Email forwarding passes through the complete message including all attachments, HTML formatting, embedded images, and headers. The destination inbox receives an exact copy of the original message as it was sent.
Can I forward to email addresses on the same domain?
No. You cannot create a forwarder where both the source and destination use the same domain. For example, forwarding [email protected] to [email protected] will not work. Forwarding requires the destination to be an external email address on a different domain. What happens if I delete a forwarder?
Once deleted, the email address immediately stops receiving mail. Messages sent to that address will bounce back to senders with a "mailbox not found" error. You can recreate the forwarder at any time if needed.
.png&w=3840&q=75)
.png&w=2048&q=75)
