[Support Guide] How can I receive emails on my domain?

I have somewhat the same issue as threeqube:

I use the Netlify DNS. In order to use GSuite (now ‘Google Workspaces’) for email, Google wants me to first verify ownership of the domain by adding a TXT record with a verification code.

Google autodetects the domain host as NS1. I assume that I can simply create the TXT record in my Netlify DNS.

However, I did this last week and the domain still has not been verified by google. I’ve tried using a CNAME record for verification instead, but still no joy - it just keeps telling me that I need to verfify the domain.

So: The verification TXT record I set up in Netlify DNS, is that not automatically propagated to NS1?

Hi, @ulyngs. The record should be a TXT type record. I only see one of those on the domains configured for your team and it works when I test:

$ dig +noall +answer <domain redacted> TXT
<domain redacted>.	3599	IN	TXT	"google-site-verification=Ksy7o3hgE7q77-aW4mfHf5ZpPlVIlglSSkPV_i2zoL4"

I’m happy to openly discuss the actual domain name if you share it or give me permission to do so. Again, the only verification record I can see is working when I test it. If there is some other record not working, please let us know what it is and we will be happy to assist.

Thanks for looking into this, Luke!

Sure thing, I think there’s nothing that needs to be secret:

I bought the domain redd-project.org through Google Domains, then used Netlify’s DNS to make it the custom domain for redd-workshop.netlify.app.

I want to be able to email from someusername@redd-project.org and would like to use Google Workspace, as the domain is already registered through Google Domains.

  1. Google prompts me to verify that I own redd-project.org (even though I actually bought it through Google - I think this would be automatically verified if I hadn’t moved the DNS to Netlify).

  2. they prompt me to do so by adding a TXT record

  3. and they provide these steps for doing so which I’ve followed

But the verification never goes through. Any suggestions as to why that might be?

(The workaround I thought of is to move the DNS back to google’s name servers, then register with google workspace (the domain verification should now be straightforward), then afterwards move back to netlify’s DNS again)

HI, @ulyngs. Personally, I cannot explain it. The record works when I test. I’m just as confused as you are.

I’m showing the record is working:

$ dig redd-project.org txt

; <<>> DiG 9.10.6 <<>> redd-project.org txt
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41241
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;redd-project.org.		IN	TXT

;; ANSWER SECTION:
redd-project.org.	3599	IN	TXT	"google-site-verification=Ksy7o3hgE7q77-aW4mfHf5ZpPlVIlglSSkPV_i2zoL4"

;; Query time: 73 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Thu Mar 04 00:39:22 PST 2021
;; MSG SIZE  rcvd: 126

The same is shown with Google’s dig tool:

https://toolbox.googleapps.com/apps/dig/#TXT/redd-project.org

So, I cannot think of any reason why it wouldn’t work. Do they want you to perhaps use some subdomain and not the apex domain like something-here.redd-project.org? (I think they always use the apex though.) Could there be a typo in the key itself?

The WHOIS record also shows the domain settings were recently changed (Updated Date: 2021-03-03T07:47:20Z). It could be that the TTL for the previous NS records hasn’t expired:

If so, it might help to purge their DNS caches here:

Note, I did just flush the NS records for redd-project.org there and it could be that this is all that was required (but only testing would confirm so I don’t know if that is true or not).

If it still doesn’t work or if there are other questions, please let us know.

Hi @luke ,

I just returned to this today to fix the problem, and without me having done anything it is working now!

Seems it just took an unusually long time for some unknown reason :slight_smile:

Hi Luke, not sure if I just reply to this thread or make a new one, but I am also having trouble getting emails working. I recently got my site hosted on Netlify and that is working fine. Apparently I can only embed one media per post so I have added links to the other relevant screens.

My domain was registered with Crazy Domains and it points to your name servers:

My old hosting was with DreamIt and they also take care of my emails as well. I have several sites registered with them, but only want my Artemist site to be hosted by Netlify. They told me that I need the zone editor part of the cpanel for the relevant email info for you guys. It looks like this:

From there I followed the instructions here and added MX records to my domain:

add also added the TXT field for good measure (not sure if I have done this correctly)

And this is the server connection settings for my email using Thunderbird:

So after all that I still get “failed to connect to server ‘mail.artemist.com.au’” each time I try and check my email.

I would REALLY appreciate it if you or someone could help. I love the Netlify platform and really want to make this a part of new business but obviously I need to get my email working too!

Thanks very much in advance…

Your MX records need to point to your mail server, not to another DNS service. However, the way you have your DNS set up your name servers are with Netlify and Netlify does not do self
hosted e-mail. You need to use a stand-alone e-mail such as ProtonMail, Gmail, etc.

Really? So if I use Netlify to host my Artemist site there is no way of being able to use things like admin@artemist.com.au or info@artemist.com.au?

I would have thought there would should surely have been a way?

@Paul_Haze Yes, of course you can have “private-label” e-mail, but not self-hosted. I refer you to the first post in this thread. Gmail and many others allow you to use your custom domain in your e-mail account(s), but you have to use a third-party, you cannot self-host an e-mail server.

So my email is hosted by DreamIt, is this considered ‘self-hosted’? I see that that Gmail can be configured to go to a custom domain (like artemist.com.au) but it seems strange that the only way to use this email address with Netlify is to set up a gmail account, have netlify point to that and then have gmail point to my email server.

Just seems a little convoluted for such a forward thinking company like Netlify…

Also there is this quote from the start of the link you posted:

Any mail provider should work with our DNS hosting, from major ones like GSuite and Outlook to your own mail server.

So you can see why I am a little confused that I can’t seem to get it work directly with my mail server at DreamIt

@Paul_Haze It depends on your account with DreamIt. If you have a separate arrangement with them to host your e-mail, then you can use DreamIt, but you need to get their MX entries to make this work.

When you use an external e-mail service, you use that service for your e-mail, you don’t point your DNS at that service and then have that service point to some other service. The whole point of the MX records is to enable you to set up a direct connection from your SOA.

This whole discussion is academic, however, because you have now removed your site from Netlify hosting.

Yes I have for now because I need to get my emails working so I wanted to try and find a solution before I hosted it again. And I do really want to get this sorted because I really like the Netlify platform and the netlify way of working. Regarding MX, I DID get MX details from DreamIt, it is in the screen shot that I posted above. I showed them the steps that Netlify were suggesting to get emails fowarded to them, and they said that it should work using the details I entered above. I would be grateful if you could look over my post, and my screenshots in particular and let me know if I missed anything?

@Paul_Haze I don’t know what the DreamIt mail servers are, but anything with “ns” in the sub domain looks wrong to me. The “web” sub domain doesn’t look very confidence-inspiring either, but if that’s what they told you then that’s what you need to use for your MX entries.

Hi Paul,

MX settings get frustrating real quick and a pain to debug. I don’t want to cause you a bunch of work again, but in your original screen shots I didn’t see the CNAME record for mail.artemist.com.au. Maybe I missed it or it was off the screenshot. Could that have been the problem with the mail server not resolving?

BTW: All your MX records look consistent with the current working settings when I do a MX lookup on your domain. Also, another note, mail.artemist.com.au would have to resolve back to the DreamIt servers for this to work if that is not how you had it setup.

Regards,
Tony

Hi, @Paul_Haze. We have a support guide about moving to Netlify DNS and preventing email downtime here:

There is a section about what to do when email services break because the required DNS records were not manually copied in advance.

The solutions are to either copy the missing records to Netlify or reverting to the previous DNS service and using the external DNS instructions instead of Netlify DNS.

If there are questions about either solution, please let us know.

I have bought the email package at one.com and host my website on netlify. In order to make email work again I had to add their MX record to the name server. However, now my email alias still doesn’t work, how could I make this work?

Hey there @Vincent_Lamoen :wave:

Have you read through these two support guides? They outline appropriate steps here!

If you have read these guides, followed the steps, and are still encountering issues please let us know! In your response, please include your site name.

I use email from domain https://sosanhgia.com.vn but i can’t set up the DNS records
How to fix it? , thanks

Hey there, @sosanhgiacomvn :wave:

Thanks for reaching out! Welcome to the Netlify Forums. Have you read the two support guides I linked in my above comment? Those are two good places to start, as well as our configure DNS docs.