DNS Lookup Tests
DNS Lookup tests
You set the following fields on the Definition and Pass Criteria tabs of a test profile. For how the tabs work, see Definition tab and Pass Criteria tab.
A DNS Lookup test asks a DNS server to resolve a domain name and checks the records that come back.
Definition fields
-
Target Domain (required): The domain name to resolve, for example
example.com. -
Record Type: The type of address record to request. A returns IPv4 addresses, AAAA returns IPv6 addresses, and A+AAAA returns both. The default is A.
-
DNS Server (Optional): The IP address of the DNS server to query, for example
8.8.8.8. Leave the field blank to use the DNS server that is configured on each endpoint. -
Timeout (s): How long the endpoint waits for the DNS server to respond before the run fails. The default is 30 seconds.
Pass criteria
-
Minimum Number of Records Returned: The fewest records a passing run can return. The minimum and default value is one.
-
Expected Resolved IPs (optional): One or more IP addresses, separated by commas, that you expect the domain to resolve to. Leave the field blank to accept any address. When you enter addresses, choose how Core Assurance compares them with the addresses the DNS server returns. See Expected IP comparison options.
-
Max Response Time (ms): The longest time a passing run can take to resolve the name.
Expected IP comparison options
The comparison option decides how strictly the returned addresses must match the addresses you expect. The examples below use an expected list of 10.0.0.1, 10.0.0.2.
|
Option |
A run passes when |
Example of a passing result |
|---|---|---|
|
Exact Match |
The returned addresses are exactly the same as the expected addresses, with none missing and none extra. Use Exact Match, the default, when a name must always resolve to a fixed set of addresses. |
|
|
In |
Every returned address is in the expected list. The server can return fewer addresses than you list. Use In when a service rotates through a known pool of addresses and you want to catch any address outside the pool. |
|
|
Contains |
The returned addresses include every expected address. The server can also return other addresses. Use Contains when specific addresses must always be present. |
|
|
Intersects |
At least one returned address is in the expected list. Use Intersects for the loosest check, when any one of several known addresses is acceptable. |
|
If the server returns records but the records do not satisfy the comparison, the run fails with the EXPECTED_IP_MISMATCH code.
For the failure codes a DNS Lookup test can return, see DNS Lookup failure codes.