Phone: (469) 634-4200

dsTest, Developing Solutions, DNS Testing

dsTest supports performance testing of the Domain Name System (DNS) network. With our IP Client simulators, your can initiate DNS queries at a programmable and sustainable rate to test the capacity of DNS server(s). The IP Client nodes can initiate DNS Query events with configurable rates and response timeouts. Up to 1000 IP Clients can be specified, with queries initiated toward the DNS server network on a round-robin fashion.

DNS tests can be configured for validation of query responses, supporting validation of DNS queries by IP address or by a user configurable string to represent interim responses which do not result in the ending IP address.

See our Use Case for DNS Testing.

Implementation

Domain names to be translated can be configured into the dsTest database via a csv formatted file.

Both ANSI and ITU networks types are supported, and UDP, TCP, and SCTP transport protocols are supported.

A list of events that can be generated by the DNS application can be found here.

As with all dsTest products, the node configurations and test scenarios are easily defined and configured with XML files that are validated against a published XML Schema to avoid invalid definitions. With our dsClient GUI, you can create, run, and archive tests, capture, graph and archive operational measurements, capture real-time data flows, and manage your dsTest servers and testing scenarios with a standalone application that runs on your PC.

Validation Functionality

A (IPv4) and AAAA (IPv6) — The response will be in the form of an IP address which will be compared to the user configurable expected IP address in the test.

PTR (Domain Name Pointer) — The response will be in the form of a Domain Name which will be compared to the user configurable expected string answer in the test.

NS (Authoritative Name Server) — The response will be in the form of a Domain Name. If there are multiple Domain Name answers in the response, only the first one will be chosen. This Domain Name will be immediately compared to the user configurable expected string answer in the test. If validation occurs at this point, the query will be complete. If the resolve to IP address element is enabled, the Domain Name will not be validated. Instead, the request will continue until it’s resolved to an IP address which will be compared to the specified IP address in the test.

MX (Mail Exchange) — The response will be in the form of a Domain Name with a preference value. If there are multiple Domain Name answers in the response, only the one with the lowest preference value will be chosen. This Domain Name will be immediately compared to the user configurable expected string answer in the test. If validation occurs at this point, the query will be complete. If the resolve to IP address element is enabled, the Domain Name will not be validated. Instead, the request will continue until it’s resolved to an IP address which will be compared to the specified IP address in the test.

TXT (Text Strings) — The response will be in the form of a text string which will be compared to the user configurable expected string answer in the test.

SRV (Service Record) — The response will be in the form of a Domain Name with priority and weight values. If there are multiple Domain Names answers in the response, the one with the lowest priority and highest weight will be chosen. This Domain Name will be immediately compared to the user configurable expected string answer in the test. If validation occurs at this point, the query will be complete. If the resolve to IP address element is enabled, the Domain Name will not be validated. Instead, the request will continue until it’s resolved to an IP address which will be compared to the specified IP address in the test.

NAPTR (Naming Authority Pointer) — The response can have a replacement string or a regular expression which can result in a text string or potentially another request Type such as SRV. The response will have an order and preference value. If there are multiple answers in the response, the one with the lowest order and lowest preference will be chosen. The resulting text string will be immediately compared to the user configurable expected string answer in the test. If validation occurs at this point, the query will be complete. If the resolve to IP address element is enabled, the text string will not be validated. Instead, the request will continue until it’s resolved to an IP address which will be compared to the specified IP address in the test.

CNAME (Canonical Name for an alias) — The response will be in the form of a Domain Name. If there are multiple Domain Name answers in the response, only the first one will be chosen. This Domain Name will be immediately compared to the user configurable expected string answer in the test. If validation occurs at this point, the query will be complete. If the resolve to IP address element is enabled, the Domain Name will not be validated. Instead, the request will continue until it’s resolved to an IP address which will be compared to the specified IP address in the test.

Operational Measurements

dsTest provides rich sets of measurements for the DNS application:

  • Transaction and transport layer attempts, successes, and failures
  • Transaction duration, transactions-per-second, and round-trip delay
  • Message and byte counters
  • Errors encountered and error indications received in messages

See our Online Help for DNS measurements and socket measurements.

You can read more about the reporting features offered with dsTest and dsClient here.

Supporting Standards