Adding Site with G Suite for E-mails

Hey everyone!

I hope you’re well. Thanks for taking the time to read my question.

I have a client whose site integrates with G-Suite to facilitate e-mails. I’m concerned about moving to Cloudflare because I’m unsure if there are any special steps I would need to take. I tried looking to see if others had similar questions and I came up empty.

Thus, are the default settings sufficient to update the DNS or do I need to do something additionally?



The only thing to do when moving to Cloudflare is to make sure all records are identical. You could potentially copy all records over and set all A/AAAA/CNAME to :grey: to keep everything identical and then move over slowly.

Thanks for the reply, Matteo!

I’m not a server guru, so this process is a bit daunting for me.

Is Cloudflare’s native porting feature sufficient to handle this automatically? If something went wrong, I worry that I do not have sufficient know how to isolate what the problem would be.


The auto-import feature is pretty good, but can’t be trusted completely.

Once you start adding your site do not change nameservers immediately. Even if it prompts you to do so.

Go to the DNS tab and make sure all records there are identical to what the previous DNS provider says. All of them.

If all they utilitize G Suite for is emails, then the only records you need to be concerned with are the MX records for the (sub)domains which receive mail. Having the proxy enabled on A/AAAA/CNAME records should not cause any issue. I also recommend configuring a DKIM and SPF record to mitigate email domain spoofing, but that practice is always a good idea, not just Cloudflare-specific.

Thank you. :blush:

How do I know which records to serve through CF and which ones to remain the same?


All records should be served through Cloudflare, unless you’re an advanced user that uses other nameservers for sub or parent domains and are delegating nameserver authority to Cloudflare for only a specific set.

I don’t think that’s exactly what @MeySite wants to know.

If you want to know which subdomains need to be served through Cloudflare’s proxy, by setting :orange: on the DNS tab, you would need to think about yourself. The hard limits are on the ports used (will edit with a link as soon as I get to a computer) and the upload size limits from the user to the server (100MB).

I would also suggest making sure HTTPS works regardless of Cloudflare before turning it on so that the whole connection from to the user to your server is encrypted. If you need a certificate and let’s encrypt isn’t an option or the configuration is long and you’d prefer a longer lasting cert you can use one of Cloudflare’s Origin Certificates that can be generated from within the SSL/TLS app of the dashboard.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.