CODEWITHSUNDEEP
google-cloud-dnsreverse-dns
Tony
Tony

Reputation: 83

Google Cloud DNS and Reverse DNS Issues for Mail Server

I have migrated my DNS records from my webhoster (their DNS has no UI) to Google Cloud DNS using Googles trail period offer (no support). I am not yet using any other Google Cloud service.

I have setup all the new PUBLIC DNS records from scratch (no transfer) on Google Cloud DNS for several domains and have also created the reverse DNS/ PTR record as a separate zone on Google Cloud DNS per the instructions. ref: https://serverfault.com/questions/779600/how-do-i-change-reverse-dns-on-google-cloud-compute/866785#866785 I have also changed the setting in my GoDaddy Registrar account to point to the Google Cloud DNS Name Servers.

However, I am experiencing same mail delivery issues and online DNS checking tools like MXToolbox and DNSStuff are reporting that there is no reverse dns / ptr record.

I found a post on the web saying that the reverse DNS/PTR record had to be done by the owner of the IP block (my webhoster) and could not be on the Google Cloud DNS if it was not one of Google IPs.

I was hoping I could avoid using my webhoster for any dns records because they have no interface and it takes them an average of 4 attempts to get it correct anytime a change is needed and this was my primary motivation for moving to the Google Cloud DNS service.

I had my webhoster create a reverse /dns record on their name servers, but despite my webhoster creating the reverse dns record, the DNS checking tools still fail on the Reverse DNS tests.

I don't think it is a propagation issue.

My question is if my Domain Registrar (GoDaddy) is now pointing to Google Cloud DNS as the primary/authoritative DNS source, how is the PTR/Reverse DNS record on my webhosters DNS server ever going to be found / discovered? I did not see anything in the Google Cloud DNS interface that would allow me to point to the webhosters DNS servers for just the Reverse/PTR DNS record entry.

A am a loss on how to resolve this reverse DNS issue for my domain mail.inspireddev.com so that my emails are reliably delivered.

Upvotes: 1

Views: 844

Answers (1)

John Hanley
John Hanley

Reputation: 81386

1) Most likely you did not update the DNS NS resource records at your registrar to point to Google DNS Servers for your domain. Use a public Internet tool like MxToolbox and run a whois check and verify the Name Servers point to your Google Cloud DNS Server.

2) In Google Cloud, DNS PTR records are configured on the IP address of a Google Cloud resource, such as Compute Engine for verified domains and not in Cloud DNS.

Delete anything you did with PTR records.

Go to Webmaster Central and verify your domain. If you modified your name servers in Step 1 above, wait a day before doing this.

To configure a PTR record, go to the Compute Engine -> Network Interface.

  • Click Enable Public DNS PTR Record.
  • Enter the domain name
  • Click Done.

You will have to wait a while for the update to complete.

Upvotes: 1

Related Questions