これらの制限は、 Trusted Cloudのすべてのプロジェクトとユーザーに適用されます。委任されていないサブドメインと、他の DNS サービスでホストされている委任は、この上限の計算には含まれません。使用可能な最後のネームサーバー シャードを占有するゾーンを Cloud DNS が作成する前に、TXT レコードでゾーンのドメイン所有権を確認する必要があります。
同じ親ドメインの複数のサブドメイン（domain.example.tld や otherdomain.example.tld など）を、同じシャードに割り当てることができます。ただし、Cloud DNS は、制限を考慮したうえで使用可能なシャードを選択する場合があります。各シャードにこのようなサブドメインを作成する場合、親ドメイン example.tld のゾーンは作成できません。
たとえば、us-central1 リージョンで新しいリージョンの外部 IP アドレスを作成するための割り当て量が十分にあっても、そのリージョンに使用可能な外部 IP アドレスがない場合、外部 IP アドレスは作成できません。ゾーンリソースの可用性は、新しいリソースを作成できるかにも影響を及ぼす可能性があります。
[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["必要な情報がない","missingTheInformationINeed","thumb-down"],["複雑すぎる / 手順が多すぎる","tooComplicatedTooManySteps","thumb-down"],["最新ではない","outOfDate","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["サンプル / コードに問題がある","samplesCodeIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-08-11 UTC。"],[[["\u003cp\u003eCloud DNS has both quotas, which are adjustable limits on shared resources, and system limits, which are fixed values that cannot be changed.\u003c/p\u003e\n"],["\u003cp\u003eQuotas are used by Google Cloud to manage resource usage, prevent overloading, and ensure fairness among users, and they generally apply at the project level, not affecting other projects.\u003c/p\u003e\n"],["\u003cp\u003eThe Cloud Quotas system monitors resource consumption, restricts access beyond allowed amounts, and allows users to request quota adjustments, including a link provided for how to do so.\u003c/p\u003e\n"],["\u003cp\u003eSystem limits on Cloud DNS resources are fixed and cannot be changed, covering various aspects like the number of peering zones, name servers per delegation, and API usage.\u003c/p\u003e\n"],["\u003cp\u003eName server shard restrictions limit the creation of public managed zones with the same or related DNS names to a maximum of five zones or five levels of subdomains to prevent conflicts.\u003c/p\u003e\n"]]],[],null,["# Quotas and limits\n\nThis document lists the quotas and system limits that apply to\nCloud DNS.\n\n- *Quotas* specify the amount of a countable, shared resource that you can use. Quotas are defined by Google Cloud services such as Cloud DNS.\n- *System limits* are fixed values that cannot be changed.\n\nGoogle Cloud uses quotas to help ensure fairness and reduce\nspikes in resource use and availability. A quota restricts how much of a\nGoogle Cloud resource your Google Cloud project can use. Quotas\napply to a range of resource types, including hardware, software, and network\ncomponents. For example, quotas can restrict the number of API calls to a\nservice, the number of load balancers used concurrently by your project, or the\nnumber of projects that you can create. Quotas protect the community of\nGoogle Cloud users by preventing the overloading of services. Quotas also\nhelp you to manage your own Google Cloud resources.\n\nThe Cloud Quotas system does the following:\n\n- Monitors your consumption of Google Cloud products and services\n- Restricts your consumption of those resources\n- Provides a way to [request changes to the quota value](/docs/quotas/help/request_increase) and [automate quota adjustments](/docs/quotas/quota-adjuster)\n\nIn most cases, when you attempt to consume more of a resource than its quota\nallows, the system blocks access to the resource, and the task that\nyou're trying to perform fails.\n\nQuotas generally apply at the Google Cloud project\nlevel. Your use of a resource in one project doesn't affect\nyour available quota in another project. Within a Google Cloud project, quotas\nare shared across all applications and IP addresses.\n\n\nThere are also *system limits* on Cloud DNS resources.\nSystem limits can't be changed.\n\nQuotas\n------\n\nTo change a quota, see\n[requesting additional quota](#requesting-additional-quota).\n\nThis table highlights important global quotas for Cloud DNS resources\nin each project. For other quotas, see the\n[**Quotas** page](https://console.cloud.google.com/iam-admin/quotas)\nin the Google Cloud console.\n\nLimits\n------\n\nUnlike quotas, where you can\n[request additional quota](#requesting-additional-quota), *limits* cannot\ngenerally be increased unless specifically noted.\n\n### API usage\n\nThe number of API requests (queries) per day is governed at the project\nlevel. All API requests count against this limit, including those made\nfrom the Google Cloud CLI and through the Google Cloud console.\n\n### Resource limits\n\n### Name server limits\n\nCloud DNS assigns every public managed zone to one of five name server\nshards. Shards are the letter before the number in an authoritative name server\nname, so `ns-cloud-e1` through `ns-cloud-e4` are the *E* shard.\n\nA new managed zone of a domain, for example `domain.example.tld`, cannot be\nassigned to a shard if any of the following already exists on the same shard:\n\n- A managed zone with the same DNS name, such as `domain.example.tld`\n- A subdomain of the DNS name, such as `sub.domain.example.tld`\n- A parent domain of the DNS name, such as `example.tld`\n\nBecause of these restrictions, the following limitations apply to public\nmanaged zones:\n\n- You can create a maximum of five zones with the exact same DNS name.\n- For any parent domain, you can create a maximum of five levels of subdomains.\n\nThese limitations apply to all projects and users in Google Cloud.\nNon-delegated subdomains and delegations hosted on other DNS services don't\ncount against this limit. Before Cloud DNS creates a zone that\noccupies the last available name server shard, you must verify the zone domain\nownership with a `TXT` record.\n\nMultiple subdomains of the same parent domain, for example `domain.example.tld`\nand `otherdomain.example.tld`, can be assigned to the same shard. However,\nCloud DNS might pick any available shard after considering the\nlimitations. If you create such subdomains in each shard, you cannot create a\nzone for the parent domain `example.tld`.\n\nYou can avoid these limitations by always creating managed zones for the parent\ndomains *before* creating zones for their subdomains.\n\nIf the child domains are already blocking all shards, follow these steps to\nfree a shard for the parent domain:\n\n1. Check the name servers for every subdomain zone to determine its shard.\n2. Find the shard (*X*) with the fewest (or least important) managed zones.\n3. Export zones in shard *X* (and change their delegations) to another DNS service.\n4. *After TTLs expire* for the original delegations, delete the managed zones for shard *X* subdomains.\n5. Create the managed zone for the parent domain; it is assigned to shard *X*.\n6. Restore the deleted managed zones for the subdomains, *restoring subdomains before any of their own sub-subdomains*. They are in new shards, so they all need updated delegations.\n\n| **Note:** Google Domains creates its own zones on shards for all domains registered through it. Shard restrictions and limits apply across these products, so a Google Domains registration uses one of the shards available for domain and subdomain zones in Cloud DNS. Conversely, if some domain has Cloud DNS zones with identical or subdomain DNS names on all the name server shards, you cannot register that domain with Google Domains until you free up a shard by using the previous steps.\n\nCheck limits\n------------\n\nYou can run the following command to look up the limits for your project. The\nfollowing example shows the total limits for the various types of objects in\nthe `my-project` project. The `totalRrdataSizePerChange` quota is measured in\nbytes and the combined total of both the additions and deletions for a change. \n\n```\ngcloud dns project-info describe my-project\n```\n\nEven though these are limits, Google Cloud tracks them internally as\nquotas, so they are labeled as quotas in the output. \n\n```\nid: my-project,\nkind: \"dns#project\",\nnumber: \"123456789012\",\nquota:\n kind: dns#quota,\n managedZones: 10000,\n resourceRecordsPerRrset: 10000,\n rrsetAdditionsPerChange: 3000,\n rrsetDeletionsPerChange: 3000,\n rrsetsPerManagedZone: 10000,\n totalRrdataSizePerChange: 100000,\n labelSets: 1000\n```\n\nYou can find the name of your default project and additional projects\nat the top of the **Home** page in the [Google Cloud console](https://console.cloud.google.com/).\n\nManage quotas\n-------------\n\nCloud DNS enforces quotas on resource usage for various reasons.\nFor example, quotas protect the community of Google Cloud users by\npreventing unforeseen spikes in usage. Quotas also help users who are exploring\nGoogle Cloud with the\n[free tier](/free/docs/gcp-free-tier)\nto stay within their trial.\n\nAll projects start with the same quotas, which you can change by\n[requesting additional quota](#requesting-additional-quota). Some quotas might increase\nautomatically based on your use of a product.\n\n### Permissions\n\nTo view quotas or request quota increases, Identity and Access Management (IAM) principals need one of the\nfollowing roles.\n\n### Check your quota\n\n### Console\n\n1. In the Google Cloud console, go to the **Quotas** page.\n\n [Go to Quotas](https://console.cloud.google.com/iam-admin/quotas)\n2. To search for the quota that you want to update, use the **Filter table**. If you don't know the name of the quota, use the links on this page instead.\n\n### gcloud\n\nUsing the Google Cloud CLI, run the following command to\ncheck your quotas.\n\n\u003cbr /\u003e\n\nReplace \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e with your own project ID.\n\n\u003cbr /\u003e\n\n```\n gcloud dns project-info describe PROJECT_ID\n \n```\n\n### Errors when exceeding your quota\n\nIf you exceed a quota with a `gcloud` command,\n`gcloud` outputs a `quota exceeded` error\nmessage and returns with the exit code `1`.\n\nIf you exceed a quota with an API request, Google Cloud returns the\nfollowing HTTP status code: `413 Request Entity Too Large`.\n\n### Request additional quota\n\nTo adjust most quotas, use the Google Cloud console.\nFor more information, see\n[Request a quota adjustment](/docs/quotas/help/request_increase).\n\n### Console\n\n1. In the Google Cloud console, go to the **Quotas** page.\n\n [Go to Quotas](https://console.cloud.google.com/iam-admin/quotas)\n2. On the **Quotas** page, select the quotas that you want to change.\n3. At the top of the page, click edit**Edit quotas**.\n4. For **Name**, enter your name.\n5. Optional: For **Phone**, enter a valid phone number.\n6. Submit your request. Quota requests take 24 to 48 hours to process.\n\n### Resource availability\n\nEach quota represents a maximum number for a particular type of resource that you can create,\nif that resource is available. It's important to note that quotas do *not*\nguarantee resource availability. Even if you have available quota, you can't create\na new resource if it is not available.\n\nFor example, you might have sufficient quota to create a new regional, external IP address\nin the `us-central1` region. However, that is not possible if there are no\navailable external IP addresses in that region. Zonal resource\navailability can also affect your ability to create a new resource.\n\nSituations where resources are unavailable in an entire region are rare. However, resources\nwithin a zone can be depleted from time to time, typically without impact to the service level\nagreement (SLA) for the type of resource. For more information, review the relevant SLA for the\nresource."]]
