The Domain Statistics feature in Public Zone provides per-domain and per-subdomain resolution statistics to help identify issues and optimize performance.
Use cases
View query volume rankings for specific domain names.
Identify subdomains with sudden spikes or drops in query volume.
Analyze query sources and resolution line hit rates for specific domain names.
Optimize resolution configurations for individual domain names.
Procedure
Go to the Alibaba Cloud DNS - Dashboard.
By default, the Resolution Dashboard > Public Zone tab is selected.
On the right, switch to the Domain Statistics tab.
The page displays an Overview with three metric cards, Statistics Summary section, and Statistics Details section.
Select a DNS resolution cluster from the drop-down list in a module's upper-right corner to view cluster-specific data.
Modules
1. Overview
These metrics only apply to domains that have DNS traffic analysis enabled.
Metric | Description |
Last 24 Hours Subdomains with Query Surges | Number of subdomains with a sudden query volume increase in the past 24 hours. Helps identify domains with abnormal traffic. |
Last 24 Hours Subdomains with Query Drop | Number of subdomains with a sudden query volume decrease in the past 24 hours. Helps identify domains with abnormal traffic drops. |
Last 24 Hours Subdomains with Denied Responses | Number of subdomains that received a negative response in the past 24 hours. Helps identify domains with potential configuration issues. |
The Overview section supports the following operations:
Click Set Period to change the statistical period (daily, weekly, or monthly).
Select a DNS resolution cluster from the drop-down list to analyze metrics by region and pinpoint traffic anomalies.
Click Alert Notifications to configure alert rules.
2. Statistics Summary
Ranking | Description |
Query Volume Ranking | Ranks domain names by query volume. Sort results and view the DNS traffic analysis status for each domain. |
Subdomain Query Ranking | Ranks subdomains by query volume. Sort results, view DNS traffic analysis status, and navigate to domain monitoring. |
Available operations:
Use the time selector to choose a time range, such as Today or a custom range.
Select a domain name from the drop-down list to filter results.
Select a sorting method from the sort drop-down list.
Version differences
Domains bound to paid instances:
Query volume statistics: Collected by default. You can view the data without enabling DNS traffic analysis.
Advanced analysis: To access in-depth metrics, such as query source statistics, route analysis, Rtype and Rcode analysis, and resolution quality analysis, you must enable DNS traffic analysis.
Domains using the free edition:
Query volume is not tracked by default. If DNS traffic analysis is not enabled, the query volume in the Statistics Summary section will display as 0.
Query volume statistics and the aforementioned advanced metrics are only visible after DNS traffic analysis is enabled.
The backend does not record historical resolution data for free edition domains; therefore, metrics prior to enabling DNS traffic analysis cannot be retrieved.
3. Statistics Details
Use the time selector to choose a time range, such as Today or a custom range.
Select a domain name from the drop-down list to filter results.
Switch between tabs to view statistics from different dimensions.
Query Volume
The query volume ranking includes domain names bound to a paid instance or have DNS traffic analysis enabled.
This tab includes:
Domain Name Query Statistics: QPS trend chart for the selected domain.
Subdomain Query Ranking: Query volume ranking for each subdomain, with a link to domain monitoring.
Data scope: The DNS query volume statistics for the main domain (zone) include the total number of DNS query requests for all subdomains under that domain.
Recommendation
Monitor query volume to verify DNS traffic migration to Public Zone. A gradual increase confirms traffic is being routed to Public Zone after migration.
Query Sources
The Global Statistics feature collects data from domains that have traffic analysis enabled. Ensure that traffic analysis is enabled for at least one domain.
Displays query source distribution by geographic location and ISP.
The tab has three sections: a map that shows the distribution by source region, numbers of DNS requests of various source regions, and top source IP by query volume.
Recommendations
Use query source analysis to track which regions route resolution requests to Public Zone. Missing traffic from certain regions or ISPs may indicate that local ISP DNS caches have not yet expired.
Resolution Route Analysis
The Global Statistics feature collects data from domains that have traffic analysis enabled. Ensure that traffic analysis is enabled for at least one domain.
Shows resolution line hit rates, including custom and default line usage.
A Route Distribution Percentage donut chart on the left shows line distribution. A table on the right lists ACL Name and DNS Query Counts for each line.
Recommendations
If you configured smart resolution with granular resolution policies, use Resolution Route Analysis to verify that the new line receives query hits, confirming the policy is active.
Rtype and Rcode Analysis
The Global Statistics feature collects data from domains that have traffic analysis enabled. Ensure that traffic analysis is enabled for at least one domain.
This tab includes:
Query Type: Displays statistics and distribution for different DNS request types, such as A, AAAA, and CNAME.
Denied Response Type: Displays statistics and distribution for negative responses, such as NXDOMAIN and NODATA.
NoteType descriptions:
NXDOMAIN (Non-Existent Domain): The queried domain name does not exist.
NXRRSET: The domain name exists, but the requested record type (RRset) does not. This is also known as a NODATA scenario.
SERVFAIL (Server Failure): The query could not be processed because of a problem with the target DNS server.
REFUSED: The DNS server refuses to perform the requested operation for policy reasons.
For example, the server may not want to provide resolution to a specific requester or may not want to perform a specific operation, such as a zone transfer.
FORMERR (Format Error): The DNS server could not interpret the query because it was malformed.
NOTIMP (Not Implemented): The DNS server does not support the requested query type.
Click a negative response type card.
The table in the upper-right section aggregates data by domain name and displays the data sorted in descending order by detection count.
Click View in the Actions column for a domain. The table in the lower-right section then aggregates data by source address and displays the data sorted in descending order by detection count.
The Statistics Details page contains a Negative response type statistics section, which displays the percentage and detection count for NXDOMAIN and NXRRSET responses. It also includes a time-series line chart and a Negative response domains table with Domain name, Detection count, and Actions columns.
Recommendations
To troubleshoot DNS resolution accuracy from endpoints, use Rtype and Rcode Analysis to locate response logs. Check the source IP's region and ISP to identify routing inaccuracies.
Resolution Quality Analysis
The Global Statistics feature collects data from domains that have traffic analysis enabled. Ensure that traffic analysis is enabled for at least one domain.
Displays resolution quality metrics and trend charts to evaluate response quality and performance.
How the resolution success rate is calculated
resolution success rate = Number of valid responses that match the requested record type (QTYPE) / Total number of resolutions
Valid response: A response that contains resource record data that matches the requested type. For example, a request for an A record succeeds if an IPv4 address is returned. The request fails if the response is NXDOMAIN, NODATA, or any other status that does not include an A record. Similarly, a request for an AAAA record succeeds only if an IPv6 address is returned.
Recommendation: The resolution success rate measures the stability and availability of your DNS service. However, this metric can be significantly affected by invalid queries, as you cannot control the domain names and record types that clients query. For example, a client might query for randomly generated, non-existent domain names. In most cases, a stable trend line indicates normal performance. You do not need to aim for the highest possible value. Instead, use this metric as part of a comprehensive analysis.
