DNS Test¶
A DNS test sends domain name resolution requests to a DNS server to check whether the resolution service is available, responds promptly, and returns DNS records that meet expectations. You can run tests from different nodes to identify domain name resolution failures or unexpected resolution results.
Create a Test¶
Go to Synthetic Monitoring > Tests > Create Synthetic Test > API Tests, and select DNS Test.
Define the Request¶
| Configuration Item | Description |
|---|---|
| Query Domain | Enter the domain name to resolve, for example example.com |
| Transport Protocol | Supports UDP (fall back to TCP on truncation), UDP, TCP, DoT, DoH, and DoQ. The default is UDP (fall back to TCP on truncation) |
| Total Timeout | Set the total timeout for a test, in seconds. The default is 10 seconds |
| DNS Server | Enter the DNS server to query. The interface supports server domain names, IPv4 addresses, and IPv6 addresses. Enter the connection information for the selected protocol |
| Port | Configure the actual listening port of the DNS service. In default UDP mode, the port is 53 |
| Name | Enter an easily identifiable test name |
When you select an encrypted transport protocol, ensure that the node can connect to the corresponding DNS service and complete the protocol-specific configuration fields displayed on the page. DoT, DoH, and DoQ transport DNS requests over TLS, HTTPS, and QUIC, respectively.
Expand Advanced Settings to configure:
- Request Settings > Fixed Connection IP: Specify the actual connection address while retaining the server domain name for TLS / HTTP identity purposes.
- DNS Options: Configure recursive resolution requests (RD), DNSSEC data requests (DO), disabled server validation (CD), and the UDP payload size. The UDP payload size ranges from 512 to 4096 bytes; the default is 1232.
Set Availability Criteria¶
Select whether the test is considered successful when all or any conditions are met, and add conditions. The following are supported: total response time, DNS records, and the AD flag in the response.
DNS record conditions support A, AAAA, CNAME, MX, NS, and TXT record types. For example, set the condition to DNS Record > At least one > A > Exists to check whether an A record is returned. This condition checks only whether the record exists. To validate the resolution result, continue configuring the expected value using the comparison methods supported by the UI.
Select Nodes and Frequency¶
Select the synthetic nodes that will run the test and set the test frequency. You can also switch to Crontab mode to configure a schedule. Save the test after confirming the configuration.
View Results¶
Find the corresponding DNS test in the test list, and go to the Synthetic Monitoring Explorer to query execution records. Analyze the results together with the test's success criteria, and avoid equating "a record was returned" with "the record content meets business expectations."
For test management, see Synthetic Tests. For query and analysis, see Synthetic Monitoring Explorer.

