[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-09-04。"],[],[],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."]]