Opened 18 months ago

Closed 18 months ago

Last modified 18 months ago

#15526 closed Bug/Something is broken (fixed)

Emails are boucing after transition to MayFirst DNS

Reported by: David Hofmann Owned by: JaimeV
Priority: Urgent Component: Tech
Keywords: DNS, emails Cc: kevin.sftp, erik.sftp
Sensitive: no


Hi MayFirst!

Here is the issue:

  • We just switched to the MF/PL DNS servers forwarding from our domain host Gandi. That works wonderfully for our websites but we only noticed today that emails sent to our domain bounce.

Here is the solution as suggested by Gandi - can this be done or do we need to find another workaround? Gandi says:

This domain is not using our LiveDNS nameservers. You can use Gandi Mail with any nameserver, but if you're experiencing issues with your email please refer to your DNS provider and ensure that the domain's DNS configuration contains the following records:

@ 10800 IN MX 10 @ 10800 IN MX 50 @ 10800 IN TXT "v=spf1 ?all"

Change History (4)

comment:1 Changed 18 months ago by David Hofmann

Cc: kevin.sftp erik.sftp added
Keywords: DNS emails added
Priority: HighUrgent
Summary: Problem with Emails combined with MayFirst DNSEmails are boucing after transition to MayFirst DNS

comment:2 Changed 18 months ago by JaimeV

Owner: set to JaimeV
Status: newassigned

Hi David,

I am assuming this is regarding e-mail for the domain. When creating a new hosting order for that domain a set of default DNS records were created for assuming you would use website and e-mail services on our servers. Those DNS records did not become active until you switched your domain to use our DNS servers.

Your mail is bouncing right now because you have yet to create any e-mail accounts on our servers. So you have two options right now. Simply create the e-mail accounts on MayFirst servers and begin using our mail server to check and send e-mail or change the MX type DNS record to point back to and continue receiving mail there.

Instructions for setting up new e-mail accounts and related tutorials can be found here:

Let us know if you need additional help resolving this.

Last edited 18 months ago by JaimeV (previous) (diff)

comment:3 Changed 18 months ago by David Hofmann

Resolution: fixed
Status: assignedclosed

Thanks for your quick reply as always! I fixed it temporarily by pointing back to the server while we get set up with using your email servers. Now we have time again - it had caught us by surprise, we hadn't thought about this aspect when switching the nameserver. Still learning. Thanks again!

comment:4 Changed 18 months ago by David Hofmann

Sensitive: unset

Please login to add comments to this ticket.

Note: See TracTickets for help on using tickets.