[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["缺少我需要的資訊","missingTheInformationINeed","thumb-down"],["過於複雜/步驟過多","tooComplicatedTooManySteps","thumb-down"],["過時","outOfDate","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["示例/程式碼問題","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-08-11 (世界標準時間)。"],[[["\u003cp\u003eThis guide provides instructions for creating a managed reverse lookup zone, which is a private zone that performs PTR lookups against Compute Engine DNS data.\u003c/p\u003e\n"],["\u003cp\u003eSetting up managed reverse lookup zones is necessary for Cloud DNS to correctly resolve non-RFC 1918 PTR records for virtual machine (VM) instances.\u003c/p\u003e\n"],["\u003cp\u003eWhen creating the zone, the DNS name suffix must end with \u003ccode\u003ein-addr.arpa\u003c/code\u003e and match the reverse lookup name of the non-RFC 1918 PTR records you intend to resolve.\u003c/p\u003e\n"],["\u003cp\u003eManaged reverse lookup zones can be created using the Google Cloud console, the \u003ccode\u003egcloud\u003c/code\u003e command-line tool, or Terraform, and the data for the zone is populated directly by the Compute Engine IP address data.\u003c/p\u003e\n"],["\u003cp\u003eA managed reverse lookup zone can be set to match any child zone, for example, a zone named \u003ccode\u003e20.in-addr.arpa\u003c/code\u003e would match any VPC-owned address beginning with \u003ccode\u003e20. * . * . *\u003c/code\u003e.\u003c/p\u003e\n"]]],[],null,[]]