이 페이지에서는 중요한 고려사항을 식별하고 도메인에 적합한 IP 주소 범위를 선택하는 데 도움을 줍니다. Microsoft Active Directory용 관리형 서비스 도메인 컨트롤러의 CIDR 범위는 설정한 후에 변경할 수 없습니다. 충돌과 시간 소모적인 실수를 피하려면 이러한 범위를 선택할 때 현재와 미래의 인프라 니즈를 신중하게 고려해야 합니다.
/24 범위 크기 사용
관리형 Microsoft AD에는 최소 /24 비공개 RFC 1918 CIDR 범위(예: 192.168.255.0/24)가 필요합니다. 더 넓은 비공개 RFC 1918 CIDR 범위를 선택할 수 있지만 이 범위는 도메인 컨트롤러 전용으로 예약되므로 /24를 사용하는 것이 좋습니다. 다른 리소스는 해당 범위의 추가 IP 주소를 사용할 수 없습니다.
관리형 Microsoft AD와 함께 사용하는 다른 Google Cloud 제품에 권장되는 다른 IP 주소 범위를 사용하려면 Google Cloud 지원팀에 문의하세요.
중첩 범위 피하기
현재 및 미래 인프라와 겹칠 수 있는 범위를 설정하지 않아야 합니다.
네트워크 전문가에게 문의
조직에 안전한 IP 주소 범위를 식별하거나 예약할 수 있는 네트워크 전문가가 있는지 확인하세요.
사용 중인 IP 주소 범위 나열
기존 인프라와의 충돌을 피하기 위해 사용 중인 IP 주소 범위를 나열한 다음 목록에 없는 IP 주소 범위를 사용할 수 있습니다.
[[["이해하기 쉬움","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,["# Select IP address ranges\n\nThis page identifies important considerations and helps you select the\nappropriate IP address ranges for your domains. CIDR ranges for\nManaged Service for Microsoft Active Directory domain controllers cannot be changed after they are set. To\navoid conflicts and time-consuming mistakes, you should carefully consider your\ncurrent and future infrastructure needs when selecting these ranges.\n\nUsing a /24 range size\n----------------------\n\nManaged Microsoft AD requires a minimum of /24 private [RFC\n1918](https://tools.ietf.org/html/rfc1918) CIDR range, such as\n`192.168.255.0/24`. Although you can select a broader private [RFC\n1918](https://tools.ietf.org/html/rfc1918) CIDR range, we recommend using\n/24 because this range is exclusively reserved for domain controllers. No other\nresources can use the additional IP addresses in the range.\n\nIf you want to use a different IP address range that is recommended by another\nGoogle Cloud product with Managed Microsoft AD, contact [Google Cloud Support](/support-hub).\n\nAvoiding overlapping ranges\n---------------------------\n\nYou should avoid setting ranges that might overlap with current and future\ninfrastructure.\n\n### Asking your network specialist\n\nCheck if there is a network specialist in your organization who can help you\nidentify or reserve safe IP address ranges.\n\n### Listing IP address ranges in use\n\nTo avoid conflicts with existing infrastructure, you can list which IP address\nranges are in use, and then use one that is not in the list. \n\n### Console\n\nTo view the IP address ranges in use on your VPC network,\nfollow these steps:\n\n1. In the Google Cloud console, go to the [**VPC**](https://console.cloud.google.com/networking/networks) page.\n\n\n [Go to VPC](https://console.cloud.google.com/networking/networks)\n\n2. Select the name of your VPC network.\n\n3. On the **VPC Network details** page, in the **IP address ranges** column,\n you can see which ranges are already in use.\n\nUse an IP address range that is not shown in the list.\n\n### gcloud\n\nTo list all subnetworks in a project, run the following\ngcloud CLI command: \n\n```\ngcloud compute networks subnets list --sort-by=NETWORK\n```\n\nUse an IP address range that is not shown in the list.\n\nLearn more about the\n[`compute networks subnets list` command](/sdk/gcloud/reference/compute/networks/subnets/list).\n\n### Considering future needs\n\nTo avoid future conflicts, consider your infrastructure plans, including the\npotential addition of authorized networks. For example, if you plan to configure\na VPN or Interconnect from the authorized networks to your on-premises networks,\nyou must select an IP address range that is not used on any of those networks.\n\nSeparating test and production environments\n-------------------------------------------\n\nTo prevent development and testing work from impacting production workloads or\nhampering the security of your deployment, consider deploying separate\ndomains for each environment.\n\nFor a simple isolated test domain, any private CIDR /24 range that isn't\nalready a subnet on your authorized VPC network or one of its\npeered networks is sufficient."]]
