Google Cloud DNS - MX records set up but GSuite not able to see them

[Rob Goehring]

Hi there,

We set up DNS hosting for our domain, mavyn.ai , at Google Cloud hosting a month or two ago. Yesterday we decided we will want user email addresses and we set up a Gsuite account, and followed a Google Support person's instructions and added the MX records for GSuite, and added the TXT verification.

However, the Gsuite support team says that their system cannot see the MX records, even though they agree that the settings I have sent as screen captures are correct. They cannot help me because they don't know Google Cloud, and have directed me here.

Any ideas?

Thanks!

Rob

[Raynel Alfonso Santana]

Hi Rob,

Thanks for the information. In this case MX Records seem to be available now [1]. Normally they show within a few hours, but sometimes it can take up to 72h before MX records are visible [2]. 

Emails sent to @mavyn.ai users, should be arriving without issues to their respective gmail accounts.

Before concluding, it’s important to mention that G Suite Support doesn’t have visibility over this platform which is exclusively for Google Cloud Platform and where you would likely to find information like service status updates and release notes.  

Have an awesome rest of your day,

[1] Google MX Records --> https://toolbox.googleapps.com/apps/dig/?lang=nl#MX/mavyn.ai 

[2] MX Propagation --> https://support.google.com/a/answer/140038?hl=en&ref_topic=2683820

[Md Zubayer]

Hello Rob,

I understand you have recently added MX records and TXT verification to use in your domain's DNS settings for Gmail with G Suite. So far I checked there is nothing on our end is blocking, I can see  both MX and TXT records.

I used Google dns server 8.8.8.8 (is the primary DNS server for Google DNS) to query (dig) :

$ dig MX mavyn.ai @8.8.8.8

; <<>> DiG 9.10.3-P4-Debian <<>> MX mavyn.ai @8.8.8.8

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32967

;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:

; EDNS: version: 0, flags:; udp: 512

;; QUESTION SECTION:

;mavyn.ai.                      IN MX

;; ANSWER SECTION:

mavyn.ai.               3599 IN MX 1 aspmx.l.google.com.

mavyn.ai.               3599 IN MX 5 alt1.aspmx.l.google.com.

mavyn.ai.               3599 IN MX 5 alt2.aspmx.l.google.com.

mavyn.ai.               3599 IN MX 10 alt3.aspmx.l.google.com.

mavyn.ai.               3599 IN MX 10 alt4.aspmx.l.google.com.

& dig TXT mavyn.ai @8.8.8.8

; <<>> DiG 9.10.3-P4-Debian <<>> TXT mavyn.ai @8.8.8.8

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 65315

;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:

; EDNS: version: 0, flags:; udp: 512

;; QUESTION SECTION:

;mavyn.ai.                      IN TXT

;; ANSWER SECTION:

mavyn.ai.               299 IN TXT "google-site-verification=7ZQUxOtrqgzMVuRtGZYrpUPjbXLM0fJcMtvJOhq3bGs"

;; Query time: 12 msec

;; SERVER: 8.8.8.8#53(8.8.8.8)

;; WHEN: Thu Oct 03 20:23:07 UTC 2019

;; MSG SIZE  rcvd: 118

These records are specifically what they should be as per this document[1]. So, it appears some MX and TXT records have been added successfully but you need to check if these records are correct or. If not, I would recommend to reach out to the GSuite support team to get further assistance.

However, If you are using Google Cloud Platform with Google Cloud DNS, you can check the available records against your DNS name from cloud DNS page in your project console. If you require to add, delete or modify the record, follow this article[2], make sure you set the resource record type accordingly.

[1] https://support.google.com/a/answer/174125?hl=en. 

[2] https://cloud.google.com/dns/docs/quickstart#create_a_new_record

[Rob Goehring]

Hi everyone,

Thanks for the reply.

I figured out the issue --- the original support person told me to include @ in the name of the MX record, and then add the records as below. That tech person, plus 3 others, all confirmed everything was correct. However it seems the inclusion of the @ caused the issue - I found this in a stackoverflow thread.

As soon as I deleted the @ in the MX record name it worked instantly.

I thought I had updated this post via an email reply but clearly it didn't work :) . Thanks to everyone that took time to respond!

Rob

[John Moody]

Rob! Thanks for sharing, this helped me a ton! 

I removed the @ and started working!