G suite gmail

i purchase domain from G suite by google and it’s hosted by Cloudflare, and i can’t receiving email on gmail , then i contact with G suite (google) they told me to sign in to Cloudflare and do some modification then i can receive email on Gmail, bu i don’t have account related to my domain in Cloudflare !!!

I do not know what to do!!!
I am a beginner

Hi @thamer.gh,

Cloudflare is not a “host”, they handle your sites DNS, but you will still have another host if you also have a website.

If you don’t have your login details, you can reset your password, but if you don’t know and can’t find out what email you signed up with, you will need to create a new account, move the domain there and manage your DNS in the new account.

Thank you domjh for helping
i did what you said , another question please , kindly find attached pic, i added MX record according to google , what about other record ,should i delete it ?

No problem, those records you highlighted in green look like Cloudflare IPs so you will need to delete them and then add any you need if you have a website as well as email on that domain name.

That looks good for GSuite now, if the nameservers are set to those on the new account, it should start working soon, if it hasn’t already.

nothing happened, what should writing in Name field ?
my domain ? or Email address ([email protected]o)?

Have you changed the domain nameservers to the new ones when you added the domain to the new account?

Those records look OK for you to receive emails in GSuite so you will need to configure your mail there, now.

What are you trying to add now, records for your website to work? If so, you will want the name to be @ and the content to be the IP address of your server.

:woozy_face: :disappointed_relieved: what is that mean ?
Domjh thank you for patient
my domain is www.honeyseason.co, and my email: [email protected]
and still i can’t receiving emails

Down below where you have the DNS records configured that you posted a screenshot of, you will see two nameservers that are something like name.ns.cloudflare.com.

When you created the new Cloudflare account, you got different nameservers, so that the new DNS records you set up work, you will need to go to wherever you registered your domain and edit the nameservers from. jessica.ns.cloudflare.com and cash.ns.cloudflare.com to whatever the two are that are listed on that page.

Currently the DNS records you have configured on the old account that you can’t access are active, by changing this, you will make it so that the new ones on the account you created are.

My domain host is CloudFlare, I have update my NS information as show in the attached image.
what else required, to activate my domain and make sure I can receive emails in my G suite gmail.

Cloudflare is not your host and you don’t want to change your nameservers at your host, anyway, but at your domain registrar.

The nameservers currently point to Jessica and cash, check on the DNS tab below your records what they should be, as I don’t think you are in the same account at the moment. The MX records you added before aren’t showing.

1 Like

please find attached files

So there are a few things missing and that you need to do.

  1. Remove the two NS records that you added in your Cloudflare DNS, those should not be there.

  2. You currently have a website on that domain, for which you don’t have any DNS records. As you can’t access the old account, check with your web host what DNS records you need. As the message at the top of your DNS screen prompts, you will need one for honeyseason.co and one for www, most likely A records pointing to your server’s IP or CNAME records pointing to a hostname that your provider specifies.

  3. Go to your domain registrar (this shows as Key-Systems GmbH (https://key-systems.net)), but will be wherever you registered and pay for the domain name. There you need to change the nameservers from cash.ns.cloudflare.com and jessica.ns.cloudflare.com to dilbert.ns.cloudflare.com and tess.ns.cloudflare.com, in orger to move the domain to your new account and make the DNS records you have configured work.

Full Whois
[email protected]:~$ whois honeyseason.co
Domain Name: honeyseason.co
Registry Domain ID: D9C479DA2FB7A4F588BD0A1BE6FE518F1-NSR
Registrar WHOIS Server:
Registrar URL: https://key-systems.net
Updated Date: 2020-09-02T12:05:34Z
Creation Date: 2020-08-28T12:05:29Z
Registry Expiry Date: 2021-08-28T12:05:29Z
Registrar: Key-Systems GmbH
Registrar IANA ID: 269
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +49.6894939685
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID:
Registrant Name:
Registrant Organization: c/o whoisproxy.com
Registrant Street:
Registrant Street:
Registrant Street:
Registrant City:
Registrant State/Province: VA
Registrant Postal Code:
Registrant Country: US
Registrant Phone:
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Admin ID:
Admin Name:
Admin Organization:
Admin Street:
Admin Street:
Admin Street:
Admin City:
Admin State/Province:
Admin Postal Code:
Admin Country:
Admin Phone:
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Tech ID:
Tech Name:
Tech Organization:
Tech Street:
Tech Street:
Tech Street:
Tech City:
Tech State/Province:
Tech Postal Code:
Tech Country:
Tech Phone:
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: cash.ns.cloudflare.com
Name Server: jessica.ns.cloudflare.com
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2020-09-11T14:55:24Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

The above WHOIS results have been redacted to remove potential personal data. The full WHOIS output may be available to individuals and organisations with a legitimate interest in accessing this data not outweighed by the fundamental privacy rights of the data subject. To find out more, or to make a request for access, please visit: RDDSrequest.nic.co.

.CO Internet, S.A.S., the Administrator for .CO, has collected this information for the WHOIS database through Accredited Registrars. This information is provided to you for informational purposes only and is designed to assist persons in determining contents of a domain name registration record in the .CO Internet registry database. .CO Internet makes this information available to you "as is" and does not guarantee its accuracy.

By submitting a WHOIS query, you agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data:  (1) to allow, enable, or otherwise support the transmission of mass unsolicited, commercial advertising or solicitations via direct mail, electronic mail, or by telephone; (2) in contravention of any applicable data and privacy protection laws; or (3) to enable high volume, automated,  electronic processes that apply to the registry (or its systems). Compilation, repackaging, dissemination, or other use of the WHOIS database in its entirety, or of a substantial portion thereof, is not allowed without .CO Internet's prior written permission. .CO Internet reserves the right to modify or change these conditions at any time without prior or subsequent notification of any kind. By executing this query, in any manner whatsoever, you agree to abide by these terms.  In some limited cases, domains that might appear as available in whois might not actually be available as they could be already registered and the whois not yet updated and/or they could be part of the Restricted list. In this cases, performing a check through your Registrar's (EPP check) will give you the actual status of the domain. Additionally, domains currently or previously used as extensions in 3rd level domains will not be available for registration in the 2nd level. For example, org.co, mil.co, edu.co, com.co, net.co, nom.co, arts.co, firm.co, info.co, int.co, web.co, rec.co, co.co.

NOTE: FAILURE TO LOCATE A RECORD IN THE WHOIS DATABASE IS NOT INDICATIVE OF THE AVAILABILITY OF A DOMAIN NAME. All domain names are subject to certain additional domain name registration rules. For details, please visit our site at www.cointernet.co <http://www.cointernet.co>.

Full Dig +trace
[email protected]:~$ dig ns honeyseason.co +trace

; <<>> DiG 9.16.1-Ubuntu <<>> ns honeyseason.co +trace
;; global options: +cmd
.			76236	IN	NS	a.root-servers.net.
.			76236	IN	NS	j.root-servers.net.
.			76236	IN	NS	l.root-servers.net.
.			76236	IN	NS	g.root-servers.net.
.			76236	IN	NS	f.root-servers.net.
.			76236	IN	NS	d.root-servers.net.
.			76236	IN	NS	c.root-servers.net.
.			76236	IN	NS	e.root-servers.net.
.			76236	IN	NS	k.root-servers.net.
.			76236	IN	NS	i.root-servers.net.
.			76236	IN	NS	h.root-servers.net.
.			76236	IN	NS	b.root-servers.net.
.			76236	IN	NS	m.root-servers.net.
;; Received 262 bytes from in 12 ms

co.			172800	IN	NS	ns1.cctld.co.
co.			172800	IN	NS	ns2.cctld.co.
co.			172800	IN	NS	ns3.cctld.co.
co.			172800	IN	NS	ns4.cctld.co.
co.			172800	IN	NS	ns5.cctld.co.
co.			172800	IN	NS	ns6.cctld.co.
co.			86400	IN	DS	43834 8 1 4957CA93E0D6029AC8BFDF039AD22E98AD721ADB
co.			86400	IN	DS	43834 8 2 A68602EC30C4E5F5D33A624D35549A7F6A2C93939D4B210BA8FA484F 3B0E084E
co.			86400	IN	RRSIG	DS 8 1 86400 20200924050000 20200911040000 46594 . xcTHFe60m0MH1lPJPBSGDttNnDPzxI6JxDyMLAcCqD0BrZHaG9ONUJek jjbAZYHCpCOZqt04/F3tWBnnSvV8O+d4HxoXHwD9TkA7MEKOKDSHnh/P FAcwkmLuAMRYlWw3aAopf3fSLnb3SpeJ4j+CFrfoAJ2ufzRCQgBeH4mT XxwI9jfqogUECY4aGnvokqwwPqf9bDWxD7bi1dDWBnLqkFAuyueZYAH9 9QWy5k80shVJniGKunvGUZGVucHYIuA7YgGl/esh8NEOts520RxKk9zq pYTWM5HDYIlbJaBFNh6MDgYdbXllwR8ia44ChA58bxWN+eDUQjEm7aP0 VD5mZA==
;; Received 792 bytes from in 12 ms

honeyseason.co.		3600	IN	NS	cash.ns.cloudflare.com.
honeyseason.co.		3600	IN	NS	jessica.ns.cloudflare.com.
131vnuv1malje6dnud9fsaqdrqcs5i91.co. 86400 IN NSEC3 1 1 1 F873A2F5 1333JQB199O7K2M508HU8IOU1OB37TFG NS SOA RRSIG DNSKEY NSEC3PARAM
131vnuv1malje6dnud9fsaqdrqcs5i91.co. 86400 IN RRSIG NSEC3 8 2 86400 20201006081455 20200906080521 64278 co. aRrdhpVkYJyOjcIooRVH/I4K5ZVtnVdYFkFrKpeKbv1tiAGiXtgJoqNT QQr7FblFEIUsAgKmzXexMwlCnBRnIsd8ccKw721XCk3P5obgtICBcMyF WNVUe8RR3/hXKeMb3AWCfv2cK8NXI+9a5PWd1GFXJiKhWS7577aegn6N 6gJnVM+TpUNJdgz6PRqH+3ZXz6Y1GL5G37r6m7gk7b2/PA==
ud1kt5a4omb0eqrj5qd5d52pv7reo2r3.co. 86400 IN NSEC3 1 1 1 F873A2F5 UD22BAL4T6R3JELLL087477HUENHQH52 NS DS RRSIG
ud1kt5a4omb0eqrj5qd5d52pv7reo2r3.co. 86400 IN RRSIG NSEC3 8 2 86400 20201006164348 20200906160057 64278 co. FL9UEQ5E4VT/pFZGanl/rem6XcXM6pDfYIGqYsTCeM8/tYEiyuihEqs7 FZ9nm+HrWVIOFCl7/lIGPopYi1HtrcmGBjU5Cu1eD/8B3elCoLm/cFGi lDf92hLyTJnFJXKiIUT9NnG8vo05FBqWD0E2V1CNHIwvyvJUZxg+P/pE u8ld7aRtIBPyPw4fWkCeFAQNPy7wfnQ+mBgA2iFtqicL1w==
;; Received 684 bytes from 2001:502:ad09::21#53(ns2.cctld.co) in 12 ms

honeyseason.co.		86400	IN	NS	cash.ns.cloudflare.com.
honeyseason.co.		86400	IN	NS	jessica.ns.cloudflare.com.
;; Received 101 bytes from 2803:f800:50::6ca2:c0ab#53(jessica.ns.cloudflare.com) in 12 ms

1 Like

additional to @domjh correct answer I will just drop here some useful instructions:

for people that may land in this page

1 Like

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