[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-03-26。"],[[["This guide provides instructions for creating a managed reverse lookup zone, which is a private zone that performs PTR lookups against Compute Engine DNS data."],["Setting up managed reverse lookup zones is necessary for Cloud DNS to correctly resolve non-RFC 1918 PTR records for virtual machine (VM) instances."],["When creating the zone, the DNS name suffix must end with `in-addr.arpa` and match the reverse lookup name of the non-RFC 1918 PTR records you intend to resolve."],["Managed reverse lookup zones can be created using the Google Cloud console, the `gcloud` command-line tool, or Terraform, and the data for the zone is populated directly by the Compute Engine IP address data."],["A managed reverse lookup zone can be set to match any child zone, for example, a zone named `20.in-addr.arpa` would match any VPC-owned address beginning with `20. * . * . *`."]]],[]]