Following up on this topic, as of now, ie August 2017, Google Cloud gives access to this feature as a ßeta version.
The procedure to make it work, as I did is:
(I am using this fake ip of 123.456.789.12 as an example here)
- Go to Google Cloud DNS
- Click on 'Create Zone'
- Type a new zone name like reverse-on-123-456-789-12 (but you can put
whatever you want)
- Type a DNS name that must be exactly: 12.789.456.123.in-addr.arpa.
- In the Description field, put whatever you want.
- Click 'Create'.
- On the new page showing the newly created zone, click on 'Add
Record'
- In the DNS Name, do not add anything, ie leave it as
'.12.789.456.123.in-addr.arpa'
- Select Resource Record PTR
- In the Canonical name, enter your hostname for which you want the
reverse mapping such as mx.example.com.
- Click create and you are done.
You can check the reverse with host lookup querying the dns server ns-cloud-b1.googledomains.com (or whatever else is the Google name server for that particular zone) until the propagation is fully completed.
and you will get:
12.789.456.123.in-addr.arpa domain name pointer mx.example.com
Yeah!
Addendum:
For those who are more inclined to use the CLI, let me add the working equivalent in command line:
- gcloud dns managed-zones create "reverse-on-123-456-789-12"
--description="Reverse mapping for 123.456.789.12" --dns-name="12.789.456.123.in-addr.arpa."
- gcloud dns record-sets transaction start
-z="reverse-on-123-456-789-12"
- gcloud dns record-sets transaction add
-z="reverse-on-123-456-789-12" --name="12.789.456.123.in-addr.arpa." --type=PTR --ttl=300 "mx.example.com."
- gcloud dns record-sets transaction describe
-z="reverse-on-123-456-789-12"
- gcloud dns record-sets transaction execute
-z="reverse-on-123-456-789-12"
The step 4 is just to check the content of the yaml file, so it can be skipped.
To find out what are the name servers allocated by Google for this newly created zone, do:
gcloud dns managed-zones describe reverse-on-123-456-789-12