온프레미스 워크스테이션에서 프라이빗 클라우드의 vCenter Server, NSX Manager, HCX와 같은 관리 어플라이언스에 액세스할 수 있습니다. 이렇게 하려면 호스트 이름과 IP 주소로 관리 어플라이언스를 처리할 수 있도록 DNS 주소 확인을 구성해야 합니다.
Cloud DNS를 사용하는 전역 주소 확인
VMware Engine을 사용하면 프로젝트의 Cloud DNS 영역을 피어링된 Virtual Private Cloud(VPC) 네트워크에 연결된 모든 관리 어플라이언스의 단일 DNS 변환 엔드포인트로 사용할 수 있습니다. 프라이빗 클라우드가 다른 리전에 배포된 경우에도 이를 수행할 수 있습니다.
표준 네트워크의 경우: 여러 프라이빗 클라우드 및 단일 프라이빗 클라우드에 대한 주소 확인을 구성할 때 Cloud DNS를 사용하여 전역 주소 확인을 설정할 수 있습니다.
기존 네트워크의 경우: 여러 프라이빗 클라우드에 대한 주소 확인을 구성할 때 Cloud DNS를 사용하여 전역 주소 확인을 설정할 수 있습니다.
단일 프라이빗 클라우드만 사용하려고 하거나 Cloud DNS를 사용하지 않으려는 경우 Cloud DNS를 사용하지 않고 주소 확인을 참조하세요.
기본적으로 Cloud DNS가 사용 설정된 모든 Virtual Private Cloud 네트워크에서 관리 영역을 확인할 수 있습니다.
표준 네트워크의 경우: 표준 VMware Engine 네트워크에 연결된 프라이빗 클라우드를 만들면 연결된 관리 DNS 영역이 생성되고 관리 어플라이언스 항목이 자동으로 채워집니다.
이 표준 VMware Engine 네트워크가 VPC 또는 다른 VMware Engine 네트워크와 피어링된 Virtual Private Cloud인 경우 관리 DNS 영역 바인딩이 자동으로 생성됩니다.
이렇게 하면 해당 네트워크의 Google Cloud VM에서 관리 어플라이언스를 확인할 수 있습니다.
Virtual Private Cloud 피어링을 생성하지 않으려는 경우 관리 DNS 영역 바인딩을 수동으로 만들 수도 있습니다.
기존 네트워크의 경우: Virtual Private Cloud 네트워크와 기존 VMware Engine 네트워크 간에 비공개 연결이 생성되면 Google에서 자동으로 DNS 피어링을 만들어 모든 Google Cloud VM을 확인합니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2024-12-21(UTC)"],[],[],null,["# Configuring on-premises DNS for management appliance access\n===========================================================\n\nYou can access management appliances like vCenter Server, NSX Manager, and HCX\non a private cloud from on-premises workstations. To do so, you must configure\nDNS address resolution so that management appliances can be addressed by their\nhostnames and IP addresses.\n\nGlobal address resolution using Cloud DNS\n-----------------------------------------\n\nVMware Engine lets you use a Cloud DNS zone in your\nproject as a single DNS resolution endpoint for all connected management\nappliances in a peered Virtual Private Cloud (VPC) network. You can do this\neven if your private clouds are deployed across different regions.\n\n- For standard networks: when configuring address resolution for multiple and\n single private clouds, you can set up global address resolution using\n Cloud DNS.\n\n- For legacy networks: when configuring address resolution for multiple\n private clouds, you can set up global address resolution using Cloud DNS.\n If you only plan to have a single private cloud, or don't intend to use\n Cloud DNS, see\n [Address resolution without using Cloud DNS](#address-resolution).\n\nBy default, you can resolve the management zone from any of your Virtual Private Cloud\nnetworks that has Cloud DNS enabled.\n\n- For standard networks: when you create a private cloud that is linked to a\n standard VMware Engine network, an associated management DNS zone\n is created and auto-populated with the management appliances entries.\n\n If this standard VMware Engine network is\n [Virtual Private Cloud peered](/vmware-engine/docs/networking/peer-vpc-network) with a VPC or another\n VMware Engine network, a\n [management DNS zone binding](/vmware-engine/docs/networking/howto-private-cloud-management-dns) is automatically created.\n This ensures resolution of management appliances from your Google Cloud\n VMs on that network.\n\n You can also manually create a management DNS zone binding if you don't want\n to create the Virtual Private Cloud Peering.\n- For legacy networks: when a [private connection](/vpc/docs/configure-private-services-access#creating-connection)\n is created between your Virtual Private Cloud network and a legacy\n VMware Enginenetwork, Google automatically creates DNS peering,\n ensuring resolution from any of your Google Cloud VMs.\n\nTo resolve addresses from an on-premises network using Cloud DNS,\ndo the following:\n\n1. [Enable inbound DNS forwarding on the Virtual Private Cloudnetwork](/dns/docs/best-practices#use_dns_server_policies_to_allow_queries_from_on-premises).\n2. [Identify the DNS server addresses to use on-premises](/dns/docs/policies#list-in-entrypoints).\n3. [Create a conditional forwarder on your on-premises DNS server to resolve `gve.goog`](#create-a-conditional-forwarder).\n\nAddress resolution without using Cloud DNS\n------------------------------------------\n\nTo resolve addresses without using Cloud DNS, get the IP address of\nyour private cloud's DNS server and configure the DNS:\n\n1. In the Google Cloud console, go to the **Private clouds** page.\n\n [Go to Private clouds](https://console.cloud.google.com/vmwareengine/privateclouds)\n2. Click **Select a project** and then select the organization, folder, or project that\n contains the private cloud you want to connect to.\n\n3. Click the name of the private cloud.\n\n4. Use one of the following options for the DNS configuration:\n\n - [Create a zone on the DNS server for `gve.goog`](#create-a-zone-on-the-dns-server-for-gvegoog)\n - [Create a conditional forwarder on your on-premises DNS server to resolve `gve.goog`](#create-a-conditional-forwarder)\n\n### Create a zone on the DNS server for `gve.goog`\n\nYou can set up a zone as a stub zone and point to the DNS servers on the private\ncloud for name resolution. This section provides information on using a BIND\nDNS server or a Microsoft Windows DNS server.\n| **Note:** In this documentation we use `gve.goog` as a generic reference for a zone. If you have more than one private cloud, you need to specify the distinct zone that you want. For example, `guid.region.gve.goog example: ab123456.australia-southeast1.gve.goog`.\n\n#### Create a zone on a BIND DNS server\n\nThe file and parameters to configure can vary based on your individual\nDNS setup.\n\nFor example, for the default BIND server configuration, edit the\n`/etc/named.conf` file on your DNS server and add the following zone\ninformation: \n\n```\nzone \"gve.goog\"\n{\n type stub;\n masters { IP address of DNS servers; };\n file \"slaves/FILE_NAME.db\";\n};\n```\n\n#### Create a zone on a Microsoft Windows DNS server\n\n1. Right-click the DNS server and select **New zone**.\n2. Select **Stub zone** and click **Next**.\n3. Select the appropriate option depending on your environment and click **Next**.\n4. Select **Forward lookup zone** and click **Next**.\n5. Enter the zone name and click **Next**.\n6. Enter the IP addresses of the DNS servers for your private cloud that you obtained from the Google Cloud console.\n7. Click **Next** as needed to complete the setup.\n\n### Create a conditional forwarder\n\nA conditional forwarder sends all DNS name resolution requests to the designated\nserver. With this setup, any request to `*.gve.goog` is forwarded to the DNS\nservers located on the private cloud. The following sections show how to set up\nforwarders on different types of DNS servers.\n\n#### Create a conditional forwarder on a BIND DNS server\n\nThe specific file and parameters to configure can vary based on your individual\nDNS setup.\n\nFor example, for the default BIND server configuration, edit the\n`/etc/named.conf` file on your DNS server and add the following conditional\nforwarding information: \n\n```\nzone \"gve.goog\" {\n type forward;\n forwarders { IP address of DNS servers; };\n};\n```\n\n#### Create a conditional forwarder on a Microsoft Windows DNS server\n\n1. Open the DNS Manager on the DNS server.\n2. Right-click **Conditional forwarders** and select the option to add a conditional forwarder.\n3. Enter the DNS domain and the IP address of the DNS servers in the private cloud, then click **OK**."]]
