This page provides instructions about how to create a managed reverse lookup zone. For detailed background information, see Managed reverse lookup zones .
A managed reverse lookup zone is a private zone with a special attribute that instructs Cloud DNS to perform a PTR lookup against Compute Engine DNS data. You must set up managed reverse lookup zones for Cloud DNS to correctly resolve non-RFC 1918 PTR records for your virtual machine (VM) instances.
To create a new managed reverse lookup private zone, complete the following steps.
Console
-
In the Google Cloud console, go to the Create a DNS zonepage.
-
For the Zone type, select Private.
-
Enter a Zone namesuch as
my-new-zone. -
Enter a DNS namesuffix for the zone. The suffix must end with
in-addr.arpato be a reverse zone. This DNS name must match the reverse lookup name of the non-RFC 1918 PTR records that you are trying to resolve through Cloud DNS. For example, if you are trying to match the PTR record for20.20.1.2, you must create a reverse lookup zone with the DNS name of2.1.20.20.in-addr.arpa. -
Optional: Add a description.
-
Under Options, select Managed reverse lookup zone.
-
Select the networks to which the private zone must be visible.
-
Click Create.
gcloud
Run the dns managed-zones create
command:
gcloud dns managed-zones create NAME \ --description= DESCRIPTION \ --dns-name= DNS_SUFFIX \ --networks= VPC_NETWORK_LIST \ --visibility=private \ --managed-reverse-lookup
Replace the following:
-
NAME: a name for your zone -
DESCRIPTION: a description for your zone -
DNS_SUFFIX: the DNS suffix for your reverse zone that must end in.in-addr.arpa; typically, reverse zones take the form${ip_block_in_reverse}.in-addr.arpa -
VPC_NETWORK_LIST: a comma-delimited list of VPC networks that contain the Google Cloud resources to whichPTRrecords resolve
Terraform
What's next
- To work with managed zones, see Create, modify, and delete zones .
- To find solutions for common issues that you might encounter when using Cloud DNS, see Troubleshooting .
- To get an overview of Cloud DNS, see Cloud DNS overview .

