Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
A resolução de DNS está disponível em instâncias particulares que executam o
Cloud Data Fusion versão 6.7.0 ou mais recente. Ele permite usar nomes de host ou
nomes de domínio para origens e destinos ao projetar seu pipeline em uma instância privada do
Cloud Data Fusion para não precisar mudar a definição do pipeline
durante o failover.
Sem ele, você usa endereços IP codificados, o que é problemático quando os endereços mudam em caso de failover em implantações de alta disponibilidade. A resolução de DNS é recomendada ao projetar um pipeline em uma instância privada e quiser recuperar o esquema, executar prévias, organizar e testar conexões.
O Cloud Data Fusion usa o peering de rede VPC para estabelecer a conectividade de rede com sua rede VPC ou VPC compartilhada. Isso permite que o Cloud Data Fusion acesse recursos na sua rede usando endereços IP internos.
Ao configurar, faça o seguinte:
Digite um Nome para a conexão de peering.
Em Sua rede VPC, escolha a rede em que você criou a instância do Cloud Data Fusion.
Em Rede VPC com peering, escolha Em outro projeto.
Em Nome da rede VPC, insira
INSTANCE_REGION-INSTANCE_ID.
Substitua:
INSTANCE_REGION: a região em que
você criou a instância do Cloud Data Fusion.
INSTANCE_ID: o ID da
instância do Cloud Data Fusion.
Em Trocar rotas personalizadas, clique em Exportar rotas personalizadas. Isso permite trocar todas as rotas personalizadas definidas na sua rede VPC com a rede VPC de locatário.
Clique em Criar.
Se o peering de rede VPC for configurado corretamente, o Status na página de detalhes da rede VPC será Ativo.
Criar uma zona de DNS particular gerenciada
Para resolver nomes de domínio no Cloud Data Fusion, crie uma zona DNS privada gerenciada na mesma rede VPC ou VPC compartilhada usada para o peering de rede VPC. Para mais informações, consulte
Criar uma zona particular.
Console
Para criar uma zona de DNS gerenciada particular, faça o seguinte:
No console do Google Cloud , acesse a página Criar zona de DNS.
Em Redes, selecione a rede VPC ou VPC compartilhada usada para o peering de rede VPC.
Clique em Criar.
Criar um conjunto de registros na zona DNS
Crie o conjunto de registros na zona DNS que tem os endereços IP internos a serem resolvidos ao projetar o pipeline. Para mais informações, consulte
Adicionar um registro.
Console
Para criar o conjunto de registros, faça o seguinte:
No console do Google Cloud , acesse a página Cloud DNS.
Clique na zona para a qual você quer criar um conjunto de registros de recursos.
Na página Detalhes da zona, clique em Adicionar padrão.
Em Nome do DNS, insira um nome de domínio que precisa ser resolvido durante o tempo de design.
Insira os detalhes do tipo de registro. Para o endereço IPv4, forneça o endereço IP interno do gravador ou da origem a ser usado no pipeline. Para mais
informações sobre tipos de registros, consulte
Adicionar um registro.
Clique em Criar.
Adicionar peering de DNS em uma instância
Console
Para criar o peering de DNS no console do Google Cloud , faça o seguinte:
Abra a instância.
No console Google Cloud , acesse a página do Cloud Data Fusion.
Clique em Instâncias e, depois, no nome da instância para acessar a página Detalhes da instância.
Para garantir que a conta de serviço do Cloud Data Fusion tenha as permissões necessárias para criar um peering de DNS em uma rede VPC compartilhada, peça ao administrador para conceder à conta de serviço do Cloud Data Fusion o papel do IAM de peer de DNS (roles/dns.peer) no projeto host da VPC compartilhada.
O administrador também pode conceder à conta de serviço do Cloud Data Fusion as permissões necessárias por meio de papéis personalizados ou outros papéis predefinidos.
[[["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-09-04 UTC."],[[["\u003cp\u003eDNS resolution, available in Cloud Data Fusion version 6.7.0 or later in private instances, enables the use of hostnames or domain names for pipeline sources and sinks, eliminating the need to change pipeline definitions during failover.\u003c/p\u003e\n"],["\u003cp\u003eTo use DNS resolution, create a private Cloud Data Fusion instance (version 6.7.0 or later), set up VPC Network Peering, create a managed private DNS zone, and add record sets with internal IP addresses for domain name resolution.\u003c/p\u003e\n"],["\u003cp\u003eDNS peering can be added to a Cloud Data Fusion instance through the console or the REST API, by providing a DNS peering ID, domain name, target project, and network.\u003c/p\u003e\n"],["\u003cp\u003eIn shared VPC networks, DNS resolution requires creating private zones in the host project or setting them up in a service project with cross-project binding, and the Cloud Data Fusion Service Account needs the \u003ccode\u003eroles/dns.peer\u003c/code\u003e IAM role.\u003c/p\u003e\n"]]],[],null,["# Resolve domain names or hostnames\n\nDNS resolution is available in private instances running in\nCloud Data Fusion version 6.7.0 or later. It lets you use hostnames or\ndomain names for sources and sinks when you design your pipeline in a private\nCloud Data Fusion instance so that you don't have to change the pipeline\ndefinition during failover.\n\nWithout it, you use hard-coded IP addresses, which are problematic when the\naddresses change in the event of a failover in highly-available deployments. DNS\nresolution is recommended when you design a pipeline in a private instance and\nwant to retrieve schema, run previews, wrangle, and test connections.\n| **Note:** Internal IP address resolution is also available with VPC Peering in all Cloud Data Fusion versions.\n\nFor more information, see\n[DNS resolution in Cloud Data Fusion](/data-fusion/docs/concepts/networking#dns-resolution).\n\nBefore you begin\n----------------\n\n### Create a private instance\n\nCreate a private instance in Cloud Data Fusion and set up a VPC network or\nshared VPC network in the instance with the following steps.\n\n1. [Create a private Cloud Data Fusion instance](/data-fusion/docs/how-to/create-private-ip).\n When you create the instance, choose the following options:\n\n 1. Choose version 6.7.0 or later.\n 2. In the **Network** field, choose the appropriate associated network for the private connection.\n 3. Enter any other instance details and click **Create** . For information about all fields, see [Create a private Cloud Data Fusion instance](/data-fusion/docs/how-to/create-private-ip).\n2. [Set up VPC Network Peering](/data-fusion/docs/how-to/create-private-ip#set-up-vpc-peering).\n\n Cloud Data Fusion uses VPC Network Peering to establish network\n connectivity to your VPC or shared VPC network. This lets\n Cloud Data Fusion access resources on your network through internal IP\n addresses.\n\n When you set it up, do the following:\n 1. Enter a **Name** for your peering connection.\n 2. For **Your VPC network**, choose the network where you created your Cloud Data Fusion instance.\n 3. For **Peered VPC network** , choose **In another project**.\n 4. For **Project ID** , enter the [tenant project ID](/data-fusion/docs/how-to/create-private-ip#find_your_tenant_project_ID).\n 5. For **VPC network name** , enter\n \u003cvar translate=\"no\"\u003eINSTANCE_REGION\u003c/var\u003e`-`\u003cvar translate=\"no\"\u003eINSTANCE_ID\u003c/var\u003e.\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003eINSTANCE_REGION\u003c/var\u003e: the region in which you created your Cloud Data Fusion instance.\n - \u003cvar translate=\"no\"\u003eINSTANCE_ID\u003c/var\u003e: the ID of the Cloud Data Fusion instance.\n 6. For **Exchange custom routes** , click **Export custom routes**. This\n allows for exchanging any custom routes defined in your VPC network with\n the tenant VPC network.\n\n 7. Click **Create**.\n\n If the VPC Network Peering is successfully set up, the **Status** on the VPC\n network details page is **Active**.\n | **Note:** Create a firewall rule on your VPC network that allows for incoming SSH connections from the IP address range you specified when you created the private Cloud Data Fusion instance.\n\n### Create a managed private DNS zone\n\nTo resolve domain names in Cloud Data Fusion, create a new managed private\nDNS zone in the same VPC network or shared VPC network that was used for VPC\nnetwork peering. For more information, see\n[Create a private zone](/dns/docs/zones#create-private-zone). \n\n### Console\n\n\nTo create a private managed DNS zone, do the following:\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 **Zone name**, enter a name.\n3. For **Zone type** , click **Private**.\n4. For **DNS name**, enter a domain name.\n5. For **Options** , click **Default (private)**.\n6. For **Networks**, select the VPC network or shared VPC network that was used for VPC Network Peering.\n7. Click **Create**.\n\n### Create a record set in the DNS zone\n\nCreate the record set in the DNS zone that has the internal IP addresses to\nresolve when you design your pipeline. For more information, see\n[Add a record](/dns/docs/records#add_a_record). \n\n### Console\n\n\nTo create the record set, do the following:\n\n1. In the Google Cloud console, go to the **Cloud DNS** page.\n\n [Go to Cloud DNS](https://console.cloud.google.com/net-services/dns)\n2. Click the zone for which you want to create a resource record set.\n\n3. On the **Zone details** page, click **Add Standard**.\n\n4. For **DNS name**, enter a domain name that must be resolved during design\n time.\n\n5. Enter the record type details. For the IPv4 address, provide the internal\n IP address for the sink or source to be used in the pipeline. For more\n information about record types, see\n [Add a record](/dns/docs/records#add_a_record).\n\n6. Click **Create**.\n\nAdd DNS Peering in an instance\n------------------------------\n\n### Console\n\n\nTo create DNS peering in the Google Cloud console, do the following:\n\n1. Open your instance.\n\n 1. In the Google Cloud console, go to the Cloud Data Fusion page.\n\n 2. Click **Instances** , and then click the instance's name to go to the\n **Instance details** page.\n\n [Go to Instances](https://console.cloud.google.com/data-fusion/locations/-/instances)\n2. Click **Add DNS peering**.\n\n The **Add DNS peering** dialog opens.\n3. For **DNS peering ID**, enter a name.\n\n4. For **Domain**, enter the domain name that you used for creating the\n private DNS zone.\n\n5. For the **Target project**, select the project name where the private\n DNS zone was created.\n\n6. For the **Network**, select the VPC network name where the\n private DNS zone was created.\n\n7. Click **Save** to create the DNS peering.\n\n### REST API\n\n\nTo resolve domain and hostnames with the Cloud Data Fusion DNS Peering\nAPI, call its\n[`create()`](/data-fusion/docs/reference/rest/v1/projects.locations.instances.dnsPeerings/create)\nmethod.\n\nFor more information and methods, see the Cloud Data Fusion\n[DNS Peering API reference](/data-fusion/docs/reference/rest/v1/projects.locations.instances.dnsPeerings).\n\nDNS resolution in shared VPC networks\n-------------------------------------\n\nTo create the Cloud DNS private zones in a [shared VPC](/vpc/docs/shared-vpc)\nnetwork, create a\n[private zone](/vpc/docs/shared-vpc#shared_vpc_and_cloud_dns_private_zones) in\nthe host project and authorize access to the zone for the shared VPC network or\nset up the zone in a service project using\n[cross-project binding](/dns/docs/zones/cross-project-binding). For more\ninformation, see\n[Best practices for Cloud DNS private zones](/dns/docs/best-practices#best_practices_for_private_zones).\n\n### Required roles for shared VPC networks\n\n\nTo ensure that the Cloud Data Fusion Service Account has the necessary\npermissions to create a DNS peering in a shared VPC network,\n\nask your administrator to grant the Cloud Data Fusion Service Account the\n\n\n[DNS Peer](/iam/docs/roles-permissions/dns#dns.peer) (`roles/dns.peer`)\nIAM role on the shared VPC host project.\n\n\n| **Important:** You must grant this role to the Cloud Data Fusion Service Account, *not* to your user account. Failure to grant the role to the correct principal might result in permission errors.\nFor more information about granting roles, see [Manage access to projects, folders, and organizations](/iam/docs/granting-changing-revoking-access).\n\n\u003cbr /\u003e\n\n\nYour administrator might also be able to give the Cloud Data Fusion Service Account\nthe required permissions through [custom\nroles](/iam/docs/creating-custom-roles) or other [predefined\nroles](/iam/docs/roles-overview#predefined).\n\nFor more information, see\n[Granting access to the required service accounts](/iam/docs/granting-changing-revoking-access#granting-console).\n\nWhat's next\n-----------\n\n- Learn more about [Networking in Cloud Data Fusion](/data-fusion/docs/concepts/networking).\n- Refer to the [Cloud Data Fusion API](/data-fusion/docs/reference/rest/v1/projects.locations.instances.dnsPeerings)."]]
