All Products
Search

This Product

    :How can the number of DNS requests be calculated?

    Document Center

    :How can the number of DNS requests be calculated?

    Last Updated:May 07, 2025
    Important

    • From April 30, 2025 (UTC+8), the zones created by new users of PrivateZone are acceleration zones by default.

    • By April 30, 2026 (UTC+8), all built-in authoritative zones in regular zones will be switched to acceleration zones. This may lead to increased DNS requests and higher costs. We recommend that you mitigate the throttling of DNS requests initiated by ECS instances to avoid increased DNS requests when local cache is unavaliable.

    1. How can the number of DNS requests for a built-in authoritative acceleration zone be calculated?

      The Domain Name System (DNS) records for built-in authoritative acceleration zones are not cached. Therefore, the number of DNS requests for a built-in authoritative acceleration zone is the same as the number of DNS requests for the zone initiated within the effective scope of the zone.

    2. How can the number of DNS requests for a built-in authoritative regular zone be calculated?

      The DNS records for built-in authoritative regular zones are cached. For example, the time-to-live (TTL) for caching the DNS record of the domain name www.example.com is 60 seconds. When the first DNS request for www.example.com is initiated, the DNS request needs to be forwarded to the built-in authoritative module to query the DNS record. If only one cache server is available, the subsequent DNS requests for the domain name match the cached DNS record in the cache server within the next 60 seconds and are not forwarded to the built-in authoritative module. Theoretically, the number of DNS requests for the domain name www.example.com in a day is 1440. The number is calculated by using the following equation: 24 x 3600/60 = 1440.

      Note

      However, multiple local DNS servers whose IP address is 100.100.2.136 or 100.100.2.138 in the cloud provide DNS resolution services. As a result, DNS requests are forwarded to these cache servers. Cached DNS records are not shared among these cache servers. The DNS requests can match cached DNS records only when cached DNS records exist in each cache server. In this way, the DNS requests are not forwarded to the built-in authoritative module. Therefore, the number of DNS requests displayed in the console may be greater than the result that is theoretically calculated.

    3. How does the subdomain recursive resolution proxy affect the number of DNS requests?

      When the subdomain recursive resolution proxy is not enabled, if an Elastic Compute Service (ECS) instance within the effective scope of a built-in authoritative zone initiates a DNS request for the zone and the DNS request does not match the DNS record in the built-in authoritative module, the DNS resolution result NXDOMAIN is returned. In this case, the number of the DNS request is calculated.

      After the subdomain recursive resolution proxy is enabled, if DNS requests neither match the DNS records in the built-in authoritative module nor match forwarding rules, the DNS requests are recursively forwarded to the Internet. The number of DNS requests is calculated regardless of whether DNS records are obtained.

      Important

      Whether the number of intranet DNS requests is calculated depends on whether the DNS requests match business rules. If the DNS requests match business rules, the number of intranet DNS requests is calculated regardless of whether DNS records are obtained.