게이트웨이의 커스텀 도메인은 API 게이트웨이용 HTTP(S) 부하 분산미리보기을 구성하여 구현될 수 있습니다. 게이트웨이에 대해 HTTP(S) 부하 분산기가 설정된 다음에는 아래 단계에 따라 새 부하 분산기 서비스를 가리키도록 커스텀 도메인의 DNS 레코드를 업데이트합니다.
이 단계는 Google 관리 인증서와 함께 HTTP(S) 부하 분산기를 사용하는 경우에도 필요합니다(도메인 필요). DNS와 함께 사용될 때는 고정 IP 주소를 할당하고 사용하는 것이 좋습니다. 이 단계의 세부 안내는 DNS 제공업체에 따라 달라집니다.
부하 분산기로 트래픽을 전송하려면 커스텀 도메인의 DNS 레코드(예: my-app-domain)가 부하 분산기의 IP 주소를 가리켜야 합니다.
전역 전달 규칙의 IP 주소를 찾으려면 다음 명령어를 사용합니다.
gcloud compute forwarding-rules list
기존 커스텀 도메인 URL로 전송된 트래픽이 대신 부하 분산기를 통해 라우팅되도록 부하 분산기의 IP 주소를 가리키도록 도메인의 DNS A 또는 AAAA 레코드를 업데이트합니다. 이 변경사항이 DNS 서버에 전달되려면 짧게는 몇 초부터 길게는 몇 시간까지 걸릴 수 있습니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-04(UTC)"],[[["\u003cp\u003eConfiguring a custom domain for API Gateway involves setting up HTTP(S) Load Balancing for API Gateway.\u003c/p\u003e\n"],["\u003cp\u003eUpdating your custom domain's DNS records to point to the load balancer service is required after setting up the HTTP(S) load balancer.\u003c/p\u003e\n"],["\u003cp\u003eTo direct traffic to the load balancer, the DNS record of the custom domain must point to the load balancer's IP address(es).\u003c/p\u003e\n"],["\u003cp\u003eUpdating the domain's DNS A or AAAA record to the load balancer's IP address routes traffic through the load balancer, with DNS propagation taking varying amounts of time.\u003c/p\u003e\n"],["\u003cp\u003eUtilizing a static IP address with DNS when using an HTTP(S) Load Balancer is recommended.\u003c/p\u003e\n"]]],[],null,["# Use a custom domain with API Gateway\n====================================\n\n|\n| **Preview**\n|\n|\n| This product or feature is subject to the \"Pre-GA Offerings Terms\" in the General Service Terms section\n| of the [Service Specific Terms](/terms/service-terms#1).\n|\n| Pre-GA products and features are available \"as is\" and might have limited support.\n|\n| For more information, see the\n| [launch stage descriptions](/products#product-launch-stages).\n\nA custom domain for your gateway can be implemented by configuring [HTTP(S) Load Balancing for API Gateway^PREVIEW^](/api-gateway/docs/gateway-load-balancing). Once the HTTP(S) load balancer for your gateway is set up, follow the steps below to update your custom domain's DNS records to point to the new load balancer service.\n\nThese steps are also required when using an HTTP(S) load balancer with a Google-managed certificate (which requires a domain). Allocating and using [a static IP address](https://cloud.google.com/sdk/gcloud/reference/compute/addresses/create) is recommended when used with DNS. The specific instructions for this step depend on your DNS provider.\n\nFor more information on setting up an HTTP(S) Load Balancer for API Gateway, see [Get started with HTTP(S) Load Balancing for API Gateway^PREVIEW^](/api-gateway/docs/gateway-serverless-neg)\n\n1. To send traffic to the load balancer, the DNS record of your custom domain (for example, `my-app-domain`) must point to the IP address(es) of the load balancer.\n\n To find the IP address of your global forwarding rule, use this command: \n\n ```\n gcloud compute forwarding-rules list\n ```\n2. Update your domain's DNS A or AAAA record to point\n to the load balancer's IP address so that traffic sent to the existing custom domain URL is routed through the load balancer instead. It may take as little as several seconds or as long as several hours for DNS to propagate this change to the DNS server."]]
