Primary logo
DNSRF Corporate Logo - words and line shorter version
Search
{item._type | case 'page' 'Web page' 'blog/blog' publication 'adnewsfeed/news' 'News' 'docs/article' 'Docs'}{item.section.title} / {item.chapter.title} / {item.topic.title}  | {category.title}
{item.title}
{item.publishDate | date 'DD MMM YYYY' | append ': '}
{tag.title}
DRAFT: WILL NOT BE PUBLISHED

Resolver capability testing

Welcome to DNS Research Federation's Resolver Capability Test bed page. This is a demonstration page to facilitate on-demand testing of the DNSRF testbed using the pre-configured tests and applicable domain names. You can also use this page to test other custom domain / test combinations added for your own installations of the Resolver Capability Testing tool.

Instructions

To trigger a capability test use the following steps.

  1. Choose whether you are using a pre-configured test or one added dynamically.
  2. If using a pre-configured test, simply choose the test and click submit
  3. If using a custom domain / test combination enter both the test type and target domain name and click submit
  4. Navigate to DAP.LIVE to see results from the test as they come in.

Enter the test data

The prototype test to trigger.

The domain name to use for the selected test.

Test diagnostic

Test Type:
{testtype | case 'ipv6' 'IPv6' 'qname-minimisation' 'QName Minimisation' 'tcp-fallback' 'TCP Fallback' 'minimum-ttl' 'Minimum TTL' 'aggressive-nsec' 'Aggressive NSEC' 'dnssec' 'DNSSEC' 'dnssec-unvalidated' 'DNSSEC Unvalidated' 'dnssec-unsigned' 'DNSSEC Unsigned'}
Posted URL:
{state.request.hostname}
Request Time:
{state.request.time | date 'YYYY-MM-DD HH:m:s'}

HTTP Request Status

HTTP Request Status

HTTP Request Status

Status:
{$parent.state.request.status | equals 'sent' | ternary 'Sent' 'Not Sent'}
Response code:
{$parent.state.request.response.status}
Response:
{$parent.state.request.response.body}
Observation:
This test seems to be configured and working as expected. This test seems to be misconfigured. Please check the settings on the testbed. No HTTP request was sent. This does not necessarily mean that the test has failed. Please check the testbed logs to confirm the results.
Top