Chargeable items are: number of private domains, DNS queries, number of source IP addresses for outbound endpoints, number of DNS queries forwarded by outbound endpoints, number of source IP addresses for inbound endpoints, and number of DNS queries forwarded by inbound endpoints.
Billing for the domain list: Fees are settled daily based on the number of private domains + the volume of user domain name resolution queries.
Billing for forwarding rules: Fees are settled daily based on the number of source IP addresses for outbound endpoints (billed hourly) + the number of DNS queries forwarded by outbound endpoints.
Billing for service addresses: Fees are settled daily based on the number of source IP addresses for inbound endpoints (billed hourly) + the number of DNS queries forwarded by inbound endpoints (this item will be merged into the volume of domain name resolution queries).
The total number of private domains added under the same account. Each private domain is charged at 0.015 USD/day . If it runs for less than a full calendar day, that domain is not billed.
The number of DNS queries for all private domains under the same account is aggregated and charged at 0.004 USD/10,000 queries .
Forwarding Rules
Billable Item
Billing Type
Billing Standard
Billing Cycle
Billing Trigger Condition
Description
Number of source IP addresses for outbound endpoints
Pay-as-You-Go
USD 0.15 per IP per hour
Settled daily
Outbound endpoint added.
Under the same account, the total number of outbound endpoint IP addresses is counted. Each outbound endpoint source IP address is charged at USD 0.15/hour. If the runtime is less than 1 hour, that IP address is not billed.
Number of DNS queries forwarded by outbound endpoints
Pay-as-You-Go
USD 0.004 per 10,000 queries
Settled daily
Domain name resolution queries are forwarded to external DNS systems via outbound endpoints.
Under the same account, the total number of DNS queries forwarded by all outbound endpoints is aggregated and charged at 0.004 USD/10,000 queries.
Service Address
Billable Item
Billing Type
Billing Standard
Billing Cycle
Billing Trigger Condition
Description
Number of source IP addresses for inbound endpoints
Pay-as-You-Go
USD 0.15 per IP per hour
Settled daily
Inbound endpoint added.
Under the same account, the total number of inbound endpoint IP addresses is counted. Each inbound endpoint source IP address is charged at USD 0.15/hour. If the runtime is less than 1 hour, that IP address is not billed.
Number of DNS queries forwarded by inbound endpoints
Pay-as-You-Go
USD 0.004 per 10,000 queries
Settled daily
Domain name resolution queries are forwarded to Tencent Cloud via inbound endpoints.
Under the same account, the total number of DNS queries forwarded by all inbound endpoints is aggregated and charged at 0.004 USD/10,000 queries. Currently, this item will be merged into the domain name resolution queries volume.
Billing of value-added services
Based on the pay-as-you-go billing method, prepaid value-added services are provided. If a prepaid "Domain Package/Traffic Package" exists under your account, the fees are first deducted according to the prepaid service. The excess portion is settled the next day based on the postpaid mode. For details, see Value-added Service Package Description.
Billing example
If you add three private domains under the account A: qq.com, dnspod.cn and yun.help.
Account A receives 100,000 DNS queries from these three private domains in a day.
Then, the daily usage fee under account A is: USD 0.015 * 3 (the basic configuration fee for three private domains) + USD 0.004 * 10 = USD 0.085.
Notes
DNS queries are subject to a TTL caching mechanism. In Private DNS, the number of actual origin-pull queries is counted and used for billing. (You need to configure the local NSCD cache to reduce the number of origin-pull queries).
Note:
If the TTL forcloud.tencent.com is set to 300s and 1,000 queries are made within the TTL, only one original-pull query, made after the TTL expires, is counted for statistics and billing.
A longer TTL setting results in a lower frequency of origin-pull queries from the DNS server, a slower propagation time for domain name changes, and a reduced number of billable queries, which in turn leads to lower charges.
A shorter TTL setting results in a higher frequency of origin-pull queries from the DNS server, a faster propagation time for domain name changes, and an increased number of billable queries, which in turn leads to higher charges.
In Private DNS, even if no resolution records are configured under a private domain, the recursive DNS queries will still be billed if the "subdomain recursive DNS" feature is enabled.
Note:
In Tencent Cloud Private DNS, if you have not configured any resolution records under the cloud.tencent.com domain and have enabled the "subdomain recursive DNS" feature, the system cannot find the corresponding resolution record in Private DNS when a query is made for cloud.tencent.com or its subdomains.
Resolution Process:
Private network resolution query: The system first searches for the resolution record of cloud.tencent.com in Private DNS. Since no resolution records are configured, the query result is "Not Found".
Recursive query to the public network: Because the "subdomain recursive DNS" feature is enabled, the system recursively forwards the query request to a public network DNS server for resolution.
Public network resolution result: The public network DNS server returns the resolution result for cloud.tencent.com or its subdomains.
Billing Description:
Recursive query billing: The operation of recursively querying the public network for resolution results is billable. Each recursive query incurs a corresponding fee. For the billing standard, see the resolution query volume (USD 0.004 per 10,000 queries).
Recommendation:
Configure resolution records: To avoid recursive queries to the public network, it is recommended that you configure corresponding resolution records for cloud.tencent.com or its subdomains in Private DNS.
Disable subdomain recursive DNS: If you do not need recursive queries to the public network, you can consider disabling the "subdomain recursive DNS" feature to avoid unnecessary costs.
In Private DNS, DNS resolution queries for any domain name are billable, regardless of whether the resolution is successful or not.
Deduction from Value-Added Service Packages
Private DNS supports billing by deduction from value-added service packages. You can check the billable items on the Private DNS buy page in the Private DNS console.
For use details, see Value-Added Service Packages.
After the payment is overdue for 24 hours, the Private DNS service will be locked and relevant features disabled, but added DNS queries will continue to take effect.
After the payment is overdue for 7 days, the Private DNS service will be suspended and relevant features disallowed, and all private domains will no longer be resolved.
You cannot operate private domain settings under an account with an overdue payment, and fees incurred during this period will be charged as required. The services will be resumed after the account is topped up.
Deduction Order
Usage deduction order
Deduction order example
Suppose an enterprise user of Private DNS purchases a value-added service traffic package with a quota of 5 million queries on a certain day. If the user has a monthly free quota of 5 million queries/month and a traffic package quota of 5 million queries, and uses the product, the free quota is deducted first. After the free quota is exhausted, the traffic package quota is deducted. When both the free quota and the traffic package quota are exhausted, the billing mode automatically switches to pay-as-you-go.
Note:
If you have problems when using the product, please feel free to contact us.
