Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
Nesta página, fornecemos instruções sobre como criar uma zona de pesquisa reversa
gerenciada. Para informações detalhadas, consulte
Zonas de pesquisa inversa
gerenciadas.
Uma zona de pesquisa reversa gerenciada é uma zona particular com um atributo especial que
instrui o Cloud DNS a realizar pesquisas de PTR em dados de DNS do
Compute Engine. Você precisa configurar esse tipo de zona no Cloud DNS
para resolver corretamente os registros PTR que não são RFC 1918 das suas instâncias de
máquina virtual.
Para criar uma nova zona particular de pesquisa reversa gerenciada, siga as etapas abaixo.
Console
No console Google Cloud , acesse a página Criar uma zona de DNS.
Digite um sufixo de Nome do DNS para a zona. O sufixo precisa terminar com
in-addr.arpa para ser uma zona reversa. Esse nome de DNS precisa
corresponder ao nome da pesquisa reversa dos registros PTR não RFC 1918 que você está
tentando resolver por meio do Cloud DNS.
Por exemplo, se você estiver tentando corresponder o registro PTR a 20.20.1.2,
crie uma zona de pesquisa reversa com o nome de DNS de
2.1.20.20.in-addr.arpa.
Opcional: adicione uma descrição.
Em Opções, selecione Zona de pesquisa reversa gerenciada.
Selecione as redes em que a zona privada precisa estar visível.
gcloud dns managed-zones create NAME \
--description=DESCRIPTION \
--dns-name=DNS_SUFFIX \
--networks=VPC_NETWORK_LIST \
--visibility=private \
--managed-reverse-lookup
Substitua:
NAME: um nome para a zona;
DESCRIPTION: uma descrição para a zona;
DNS_SUFFIX: o sufixo DNS da zona reversa
que precisa terminar em .in-addr.arpa. Normalmente, as zonas inversas assumem a forma
${ip_block_in_reverse}.in-addr.arpa;
VPC_NETWORK_LIST: uma lista delimitada por vírgulas de
redes VPC que contêm os recursos Google Cloud
aos quais os registros PTR resolvem.
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-08-11 UTC."],[[["\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,["# Create a managed reverse lookup zone\n\nThis page provides instructions about how to create a managed reverse lookup\nzone. For detailed background information, see\n[Managed reverse lookup\nzones](/dns/docs/zones/zones-overview#managed_reverse_lookup_zones).\n\nA managed reverse lookup zone is a private zone with a special attribute that\ninstructs Cloud DNS to perform a PTR lookup against Compute Engine\nDNS data. You must set up managed reverse lookup zones for Cloud DNS\nto correctly resolve non-RFC 1918 PTR records for your virtual machine (VM)\ninstances.\n\nTo create a new managed reverse lookup private zone, complete the following steps. \n\n### Console\n\n1. In the Google Cloud console, go to the **Create a DNS zone** page.\n\n [Go to Create a DNS zone](https://console.cloud.google.com/net-services/dns/zones/new/create)\n2. For the **Zone type** , select **Private**.\n\n3. Enter a **Zone name** such as `my-new-zone`.\n\n4. Enter a **DNS name** suffix for the zone. The suffix *must* end with\n `in-addr.arpa` to be a reverse zone. This DNS name must match\n the reverse lookup name of the non-RFC 1918 PTR records that you are\n trying to resolve through Cloud DNS.\n For example, if you are trying to match the PTR record for `20.20.1.2`,\n you must create a reverse lookup zone with the DNS name of\n `2.1.20.20.in-addr.arpa`.\n\n | **Note:** Cloud DNS also supports matching of any child zone. For example, if you create a managed reverse lookup zone with the DNS name `20.in-addr.arpa.`, the zone matches any VPC-owned address `20. * . * . *`.\n5. Optional: Add a description.\n\n6. Under **Options** , select **Managed reverse lookup zone**.\n\n7. Select the networks to which the private zone must be visible.\n\n8. Click **Create**.\n\n### gcloud\n\nRun the\n[`dns managed-zones create`](/sdk/gcloud/reference/dns/managed-zones/create)\ncommand: \n\n```\ngcloud dns managed-zones create NAME \\\n --description=DESCRIPTION \\\n --dns-name=DNS_SUFFIX \\\n --networks=VPC_NETWORK_LIST \\\n --visibility=private \\\n --managed-reverse-lookup\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eNAME\u003c/var\u003e: a name for your zone\n- \u003cvar translate=\"no\"\u003eDESCRIPTION\u003c/var\u003e: a description for your zone\n- \u003cvar translate=\"no\"\u003eDNS_SUFFIX\u003c/var\u003e: 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`\n- \u003cvar translate=\"no\"\u003eVPC_NETWORK_LIST\u003c/var\u003e: a comma-delimited list of VPC networks that contain the Google Cloud resources to which `PTR` records resolve\n\n### Terraform\n\n resource \"google_dns_managed_zone\" \"default\" {\n name = \"my-new-zone\"\n description = \"Example DNS reverse lookup\"\n provider = google-beta\n visibility = \"private\"\n dns_name = \"2.2.20.20.in-addr.arpa.\"\n reverse_lookup = \"true\"\n }\n\n| **Note:** You cannot add records to a reverse lookup DNS zone directly; the data comes from the Compute Engine IP address data.\n\nWhat's next\n-----------\n\n- To work with managed zones, see [Create, modify, and delete zones](/dns/docs/zones).\n- To find solutions for common issues that you might encounter when using Cloud DNS, see [Troubleshooting](/dns/docs/troubleshooting).\n- To get an overview of Cloud DNS, see [Cloud DNS overview](/dns/docs/overview)."]]