Relatively extensive checks on DNS correctness with easy-to-understand results. Includes citations to sections of relevant RFCs in the event of problems. Also checks SMTP server behavior and looks for www within the zone.
Relatively extensive checks on DNS correctness with easy-to-understand results. Less detail than dnsreport.com Also checks SMTP and HTTP server behavior, based on MX records and www names.
Enumerates all the possible paths that a query could take, starting from the roots to final resolution. Tests one query type at a time. Generates quite a lot of output that is difficult to parse. The "Servers involved in resolving" table at the end is neat.
A persistent database of zones that are periodically re-checked. Associates a color-coded status with each zone. The logfiles are a little difficult to read. For example, its not immediately clear where it stops querying one nameserver and begins querying the next.
Graphically displays the relationships between a zone and its nameserver delgations, starting at one of the roots. Also includes some textual information and warnings about the zone.
This is the online demo of the ZoneCheck software. In addition to a few standard DNS checks, it also tests for TCP, UDP, and ICMP connectivity.
This tool checks nameservers for lame delegations, geographic location, matching reverse entries, open MX relays, and more.
This tool also performs a suite of checks against the authoritative nameservers for a zone.
The Perl script used by dnscheck.se.
Textually displays the hierarchy of nameservers involved in a target name. Reports on certain errors, such as lame delegation. Here is an example.
The ZoneCheck software uses ruby and provides three interfaces: CGI, CLI, and X11.
This program debugs DNS problems by making zone transfers from live servers and then validating the records that it finds. Here is an example.
This /bin/sh script calls dig and other utilities to perform consistency checks upon a zone. Here is an example.
A DNS fingerprinter in Perl. Uses an extensive list of heuristics to determine what is behind a particular nameserver. Here is an example.
A nifty /bin/bash script from William Stearns that you can run periodically to detect changes in DNS records.
© 2013 The Measurement Factory.