What are the limits of on-premises?_on-premises - Alibaba Cloud DNS

Deployment environment limits

Limitations	Limit	Description
Operating system	Alibaba Cloud Linux Anolis 8 CentOS 7 CentOS Stream 9–10 Ubuntu 22–24	Other operating systems are not supported.
Server	Physical server Virtual machine	The underlying server must use the x86 architecture. ARM servers are not supported.
CPU	Management agent node: At least 2 vCPU (if deployed separately) A parsing node requires at least 4 vCPUs when used in a standalone deployment or a mixed deployment with the management agent. Simple Log Service node: At least 2 vCPU	DNS node Minimum configuration: 4 vCPU and 8 GB memory, supports 50,000 QPS. Configuration: 8 vCPU and 16 GB memory, supports 100,000 QPS. Simple Log Service node Minimum configuration: 2 vCPU and 4 GB memory, supports 100,000 QPS. It can connect to two DNS nodes that each support 50,000 QPS. Configuration: 4 vCPU and 8 GB memory, supports 200,000 QPS. It can connect to four DNS nodes that each support 50,000 QPS. Configuration: 8 vCPU and 16 GB memory, supports 400,000 QPS. It can connect to eight DNS nodes that each support 50,000 QPS.
Memory	Management agent node: At least 4 GB (if deployed separately) Parsing node (standalone or mixed deployment): at least 8 GB Simple Log Service node: At least 4 GB
Clock speed	2.6 GHz or higher is recommended.
Storage	Test environment: At least 50 GB Production environment: At least 500 GB	The software is installed in the `/home` directory. This location cannot be changed. Reserve enough storage space in this directory.

Restrictions	Limit	Description
Number of clusters per account	15	The total number of DNS service clusters and Simple Log Service clusters under a single account cannot exceed 15.
Number of nodes per cluster	100	The number of nodes in a single DNS cluster or Simple Log Service cluster cannot exceed 100.
Cluster or node name length	128 characters	The cluster or node name cannot exceed 128 characters. The name must be unique within an account.
Node remarks length	128 characters	The remarks for a node cannot exceed 128 characters.

Maximum length: 200 characters. Minimum number of labels: 1.
Note
Labels are separated by periods (.). For example, a has one label, a.b has two labels, and a.b.c has three labels.
Maximum number of labels for a zone: 16.
Maximum number of labels for a host record: 20.
Note
The maximum number of labels for a fully qualified domain name (FQDN) is 36.
The top-level domain label must be 2 to 63 characters long. Other labels must be 1 to 63 characters long. Labels can contain hyphens (-), underscores (_), digits, and lowercase letters. Each label must start with a digit or a lowercase letter.
Note
For example, in www.aliyun.com, the com label must be 2 to 63 characters long. The aliyun and www labels must each be 1 to 63 characters long.
Reverse lookup domain names must end with .in-addr.arpa.

Limitations	Threshold	Description
Number of domain names (zones)	500	Each account can have a maximum of 500 domain names (zones), regardless of scope settings.
Number of associated DNS clusters	100	Each domain name (zone) can be associated with up to 100 DNS clusters.
Number of accounts for cross-account association of DNS clusters	None	Cross-account association of DNS clusters is not supported.
Number of DNS records	100,000	By default, you can add up to 100,000 DNS records to each domain name (zone) in a built-in authoritative accelerated zone. To exceed this limit, submit a ticket to request a quota increase. This does not apply to standard zones.
Batch operations	Limits	PrivateZone supports batch operations such as deleting domain names, importing DNS records, and pausing or enabling DNS records.

Limits	Limit	Description
Number of forwarding rules per account	1,000	A single account can have a maximum of 1,000 forwarding rules, regardless of scope settings.
Number of DNS clusters associated with a single forwarding rule	100	A single forwarding rule can be associated with a maximum of 100 DNS clusters.

Limits	Limit	Description
Number of cache reserve domain names per account	No limit	There is no limit on the number of cache reserve domain names per account.
Number of DNS clusters associated with a cache reserve domain name	100	A single cache reserve domain name can be associated with a maximum of 100 DNS clusters.

Zone-to-cluster association	Secondary DNS availability	Secondary DNS configuration
Associated only with a on-premises DNS cluster	Yes, it is.	For more information, see Secondary DNS.
Associated only with an Alibaba Cloud VPC	Active
Not associated with any cluster	Active
Associated with both a on-premises DNS cluster and an Alibaba Cloud VPC	No	Not applicable

Note

A domain name that uses Secondary DNS cannot be associated with both an Alibaba Cloud VPC and a on-premises DNS cluster.

Type	Limit	Description
Batch import domain names	Not applicable	Batch import of domain names is not supported.
Batch delete domain names	1 to 100	You can delete up to 50 domain names at a time in the console because each page displays a maximum of 50 items. You can delete up to 100 domain names at a time by calling the API operation.
Batch import DNS records	xls, xlsx, or zone	The supported file formats are xls, xlsx, and zone.
	1 to 1,000 records per operation	You can import a maximum of 1,000 DNS records at a time. Any records beyond this limit are ignored.
	2 MB per operation	The size of the imported file cannot exceed 2 MB.
Batch delete DNS records	1 to 100	The number of records you can delete in a single batch operation.
Batch pause or enable DNS records	1 to 100	The number of records you can pause or enable in a single batch operation.

Authoritative zones, cache reserve domain names, or forwarding rules cannot be associated with a on-premises DNS log cluster.
Authoritative zones, cache reserve domain names, or forwarding rules cannot be associated with a on-premises DNS cluster that has no nodes.
You cannot manage the authoritative zones, cache reserve domain names, or forwarding rules associated with a cluster that has an expired software version. To manage them, you can upgrade the cluster to the latest software version or detach the cluster.
A authoritative zone, a cache reserve domain name, and a forwarding rule zone that share the same name cannot be associated with the same on-premises DNS cluster.
Standard authoritative zones cannot be associated with a on-premises DNS cluster.