Not receiving email on GoDaddy email address

Hello everyone! I am having trouble receiving GoDaddy emails after connecting my domain to Netlify. I have entered the mx records from GoDaddy into Netlify’s DNS records and still nothing :cry: Has anyone had success in resolving an issue such as this one?
Here is the domain: https://upsafetysolutions.com

There was no error on your part, but an error had occurred on the Netlify side of things. We have found and correct the issue on our side now.

So, the records should now be working correctly. If not, please let us know and we’ll be happy to research the issue further.

(I did just test the records though so I am quite certain they are now working).

Likewise, please reply if there are any questions about this.

1 Like

Thanks for getting back to me but unfortunately I still cannot receive emails in my GoDaddy inbox.
I’m including a screenshot of MX Toolbox, it is telling me there is no DMARC Record found (apparently its a DNS issue, ps: I’m not familiar with any of this). If there is any more info you need to help me solve this issue please let me know, I need to fix this as soon as possible. @futuregerald @luke

The DMARC records will be TXT type DNS records. They probably (almost certainly) existed with the previous DNS service and they now need to be copied to Netlify.

If there are questions about how to find these records and copy them to our service, please let us know.

If you need assistance with this, please let us know domain names for the previously used DNS servers. With this information, it is normally possible to quickly retrieve the records needed.

OK, here is a screenshot of the name server domain.
I had to reset the name server so you guys are no longer handling DNS for the time being. I need to retrieve emails that were in queue then ill revert back to using Netlify for DNS.

Here are the new MX records when GoDaddy is handling DNS, the IP address is different and now the emails are (obviously) being received.

Hi @UpSafetySolutions,

Looks like you resolved the issue you were having. Thanks for the update.

im having this issue too @UpSafetySolutions @futuregerald - is there any guidance here? Im slightly confused - should i be adding unique cname records for each “name” and “target” go daddy specify and that would map to “name” and “value” of netlify side of things? For e.g. this would require me adding 5 cnames for autodiscover, sip, lyncdiscover etc?

Best,

Rory

Hi, @roryw10. I’m not familiar with all of those DNS record types so please do feel free to reply to add more details if there are still questions.

Here is an example record for a SIP service (which is done using the SVR record type):

I hope this example helps answer the questions about these DNS records and if not, again, please reply anytime.

ok i thought it would be easier to just post the settings, so they should all be cnames? @luke

For the short term i’m going to have to revert to the old setup as it’s kind of crucial for us email works, it would be great if we could get some feedback on how to configure this properly and then i can switch back over without any disruption!

@roryw10, I agree with your suggested plan. It may be helpful to switch the DNS provider back to the previous service. You can still add records at Netlify and then only enable our DNS again once you are certain all the required records are working correctly with our service.

There are ways to test the DNS records added to our service while using your previous service. For example, using the dig command’s @ option to pick a specific DNS server to query like so:

dig <QUERY GOES HERE> @dns1.p05.nsone.net 

You would replace @dns1.p05.nsone.net with an actual domain name listed in the Managed DNS settings for this domain at Netlify. This command won’t query the “official” DNS service and, instead, it will allow you to see what the records are at Netlify before you switch over to our DNS servers again. (If you leave off the @dns1.p05.nsone.net the dig command will query the “offical” DNS server for the same query. This will allow you to compare the Netlify version with the other service’s records to make sure they match.)

For the records in the screenshot above, the type of DNS record to create is listed above each set of records. There are four types of DNS records which need to be created based on that screenshot. Those types are: CNAME, MX, SRV, and TXT.

I have included an annotated image which (hopefully) will clarify which type each of the records should be:

As always, please reply here if there are other questions.

ok @luke so i tried to switch out the settings as reflected with the image anotated above (super helpful) and left it around 8 hours. It does not seem to have worked though.

I tried to use googles MX checker after making the changes - all the tests cleared apart from grumbling about : DKIM is not set up, DMARC is not set up.

I’ve reverted the site to the squarespace / godaddy set up so our mail is back online now but i would much rather be using the netlify setup.

The DKIM/DMARC issues means there are likely additional TXT type records required. Here are some links to (third-party) documentation about these types of records:

https://www.dmarcanalyzer.com/how-to-create-a-dmarc-record/
https://www.bettercloud.com/monitor/spf-dkim-dmarc-email-security/

Before enabling our Managed DNS (by changing your domains name servers to the Netlify controlled name servers listed in the Managed DNS settings), it is important to copy all required records to our service first.

The key here is the phrase “all required records”. Netlify doesn’t know what those are so you must create a complete list of all required records and copy them to the Managed DNS settings for this domain. To clarify, you must compile the list of “all required records”.

Once that is known, we are happy to assist with creating and verifying those records exist at Netlify, but the complete list of all required records is simply not information we have.

@luke sorry for the delayed reply, in terms of “all required records” i understand the point conceptually if my interpretation is that the required records are on the godaddy side? I’m struggling to see how to actually compile all required records in practice? Is it the case that the records godaddy list (as in the labelled screen shot above) are incomplete? I can attempt to get in touch with godaddy directly and hopefully i can use dig to do this?

@roryw10, I recently created a topic which covers here:

There is a section titled: I did not copy my records before switching name servers and my email (or other service) stopped working? How do I fix this?!?!

That section covers ways to resolve this.

The required records may exist already at GoDaddy (or they may not). To see if they do exist there, log into your account and navigate to the DNS configuration for your domain. This should show you all the existing records.

If those records don’t exist, the provider of your email service should be able to tell you what the correct settings are.

If you don’t have an email service provider, this topic discusses how to find one:

There are both free and paid email services available from third-parties if GoDaddy doesn’t provide one.