Provided by: libzonemaster-perl_4.7.2-1_all 
NAME
Zonemaster::Engine::Overview - The Zonemaster Test Engine
INTRODUCTION
The Zonemaster system is a quality control tool for DNS zones, produced in cooperation
between AFNIC and IIS (the top-level registries for respectively France and Sweden). It is
a successor both to AFNIC's tool Zonecheck and IIS's tool DNSCheck, and is intended to be
an improvement over both.
The system as a whole consists of the test engine and, as distributed by the project, two
different front ends. One is a command-line interface intended for use by experienced
technicians, and one is a web interface meant for use by anyone. This document only talks
about the test engine.
DESCRIPTION
Brief overview
Conceptually, the test engine consists of a number of test implementation modules
surrounded by a support framework. Anyone wanting to use Zonemaster to perform tests
communicates with the framework from the "outside", and all modules implementing tests see
the world entirely through the framework. Doing things this way lets us have features like
the ability to test domains before they are published, to record entire test runs for
later analysis and to make sure that test restults are (as far as reality allows)
predictable and repeatable.
For users of Zonemaster
If all you want to do is run tests, you need to care about four or five modules.
Zonemaster::Engine is the main access point to the framework, and it is via its methods
that you set the configuration (if needed), request that tests be started and access the
logger. The logger is where the test results end up, so that's pretty important. On top of
those, you may want to use the Zonemaster::Engine::Translator to turn the results into
human-readable messages.
There are two ways that you can get the results of a test you've requested: the simple-
but-inflexible way and the flexible-but-complex way.
The simple-but-inflexible way is that all the methods in Zonemaster::Engine that run tests
return lists of Zonemaster::Engine::Logger::Entry objects. Those lists include all the
results that the writer of the test module(s) considered important enough to return by
default. The advantage of this method is that it is extremely easy to use. The following
is a functional (if not very useful) way to run a full test and print the results from a
command line prompt:
perl -MZonemaster::Engine -E 'say "$_" for Zonemaster::Engine->new->test_zone("example.org")'
The main drawbacks of this method are that there is no choice about what messages to see,
and it's entirely synchronous. The code that started the test does not get a chance to do
anything at all until the whole test has finished, which may be several minutes later.
To get around those drawbacks there is the flexible-but-complex way, which consists of
installing a callback that gets executed every time a message is logged. It's not that
much more complicated, code-wise. The following example does roughly the same thing as
the one above:
perl -MZonemaster::Engine -E 'Zonemaster::Engine->logger->callback(sub {say "$_[0]"}); Zonemaster::Engine->new->test_zone("example.org");'
If you try running those, you'll notice two main differences. First, the second variant
prints results as they are generated. Second, it generates a lot more output. On my
machine right now, the first example gives me 94 lines of output. The second example gives
me 17684.
You can do pretty much whatever you want with the message objects in the callback
(including modifying them, although we don't promise that behavior will stay around). If
the callback code throws an exception, and that exception is not a subcless of
Zonemaster::Engine::Exception, the callback will be removed. Note also that while the
callback is running, the test engine itself is not. So think twice before you do
potentially time-consuming tasks (like sticking the message in a database) in the
callback. After waiting for responses from remote name servers (which usually stands for
more than 90% of the time used), the result logging is the single most time-consuming task
in a Zonemaster test run.
From here, you probably want to look at the documentation for Zonemaster::Engine,
Zonemaster::Engine::Logger, Zonemaster::Engine::Logger::Entry, Zonemaster::Engine::Config
and Zonemaster::Engine::Translator.
For developers of Zonemaster Test Modules
If you want to develop a test module of your own, the standard set of modules serve as
examples.
As an entry point to the "inside" of the Zonemaster framework, you want to read
Zonemaster::Engine::Zone and follow references from there. Of particular interest after
the zone class should be the Zonemaster::Engine::Nameserver and possibly
Zonemaster::Engine::Recursor classes.
If you do write your own test module, I would very much appreciate feedback on which parts
were tricky to figure out, because I'm honestly not sure what I need to explain here. So
please, if there's somethat that you think really needs to be written about, add an issue
about at <https://github.com/zonemaster/zonemaster-engine/issues>.
For developers of the Zonemaster Test Framework
Random recommendations and advice. May be replaced with more coherent developer
documentation in the future.
• Stability, predictability and reliability are more important than performance.
• Don't forget that starting with Perl version 5.18, the order in which you get the keys
out of a hash will be different every time the script is run. Get used to always
writing "sort keys %hash".
• If two (or more) test implementation modules implement the same (or very similar)
thing, it should probably be extracted into the framework.
• The unit tests run against pre-recorded data, unless the environment variable
"ZONEMASTER_RECORD" is set to a (perl-)true value. In that case, it runs against the
live DNS world and records all results for future use. Unfortunately this sometime
means that some tests fail, when we were relying on seeing certain problems in certain
domains, and those no longer look the same.
• The translation strings returned from a test module are used as keys in the GNU
gettext system, so if you change anything in them don't forget to also change the
translation ".po" files in share.
• Adding a new message tag is more work than it first looks, since it needs to be added
to the test module metadata, the default policy and the translation system in order to
be fully functional.
REFERENCES
<https://github.com/zonemaster/zonemaster>
Main repository, holding among other things our test specifications.
List of all RFCs referred to in the test specifications
• RFC0822 "STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES" <http://www.rfc-
editor.org/info/rfc822>
• RFC0919 "Broadcasting Internet Datagrams" <http://www.rfc-editor.org/info/rfc919>
• RFC0952 "DoD Internet host table specification" <http://www.rfc-
editor.org/info/rfc952>
• RFC1033 "Domain Administrators Operations Guide" <http://www.rfc-
editor.org/info/rfc1033>
• RFC1034 "Domain names - concepts and facilities" <http://www.rfc-
editor.org/info/rfc1034>
• RFC1035 "Domain names - implementation and specification" <http://www.rfc-
editor.org/info/rfc1035>
• RFC1112 "Host extensions for IP multicasting" <http://www.rfc-editor.org/info/rfc1112>
• RFC1122 "Requirements for Internet Hosts - Communication Layers" <http://www.rfc-
editor.org/info/rfc1122>
• RFC1123 "Requirements for Internet Hosts - Application and Support" <http://www.rfc-
editor.org/info/rfc1123>
• RFC1912 "Common DNS Operational and Configuration Errors" <http://www.rfc-
editor.org/info/rfc1912>
• RFC1918 "Address Allocation for Private Internets" <http://www.rfc-
editor.org/info/rfc1918>
• RFC1930 "Guidelines for creation, selection, and registration of an Autonomous System
(AS)" <http://www.rfc-editor.org/info/rfc1930>
• RFC1982 "Serial Number Arithmetic" <http://www.rfc-editor.org/info/rfc1982>
• RFC1996 "A Mechanism for Prompt Notification of Zone Changes (DNS NOTIFY)"
<http://www.rfc-editor.org/info/rfc1996>
• RFC2142 "Mailbox Names for Common Services, Roles and Functions" <http://www.rfc-
editor.org/info/rfc2142>
• RFC2181 "Clarifications to the DNS Specification" <http://www.rfc-
editor.org/info/rfc2181>
• RFC2182 "Selection and Operation of Secondary DNS Servers" <http://www.rfc-
editor.org/info/rfc2182>
• RFC2308 "Negative Caching of DNS Queries (DNS NCACHE)" <http://www.rfc-
editor.org/info/rfc2308>
• RFC2544 "Benchmarking Methodology for Network Interconnect Devices" <http://www.rfc-
editor.org/info/rfc2544>
• RFC2671 "Extension Mechanisms for DNS (EDNS0)" <http://www.rfc-
editor.org/info/rfc2671>
• RFC2822 "Internet Message Format" <http://www.rfc-editor.org/info/rfc2822>
• RFC2870 "Root Name Server Operational Requirements" <http://www.rfc-
editor.org/info/rfc2870>
• RFC2928 "Initial IPv6 Sub-TLA ID Assignments" <http://www.rfc-editor.org/info/rfc2928>
• RFC3056 "Connection of IPv6 Domains via IPv4 Clouds" <http://www.rfc-
editor.org/info/rfc3056>
• RFC3068 "An Anycast Prefix for 6to4 Relay Routers" <http://www.rfc-
editor.org/info/rfc3068>
• RFC3658 "Delegation Signer (DS) Resource Record (RR)" <http://www.rfc-
editor.org/info/rfc3658>
• RFC3696 "Application Techniques for Checking and Transformation of Names"
<http://www.rfc-editor.org/info/rfc3696>
• RFC3701 "6bone (IPv6 Testing Address Allocation) Phaseout" <http://www.rfc-
editor.org/info/rfc3701>
• RFC3849 "IPv6 Address Prefix Reserved for Documentation" <http://www.rfc-
editor.org/info/rfc3849>
• RFC3927 "Dynamic Configuration of IPv4 Link-Local Addresses" <http://www.rfc-
editor.org/info/rfc3927>
• RFC4034 "Resource Records for the DNS Security Extensions" <http://www.rfc-
editor.org/info/rfc4034>
• RFC4035 "Protocol Modifications for the DNS Security Extensions" <http://www.rfc-
editor.org/info/rfc4035>
• RFC4074 "Common Misbehavior Against DNS Queries for IPv6 Addresses" <http://www.rfc-
editor.org/info/rfc4074>
• RFC4193 "Unique Local IPv6 Unicast Addresses" <http://www.rfc-editor.org/info/rfc4193>
• RFC4291 "IP Version 6 Addressing Architecture" <http://www.rfc-
editor.org/info/rfc4291>
• RFC4343 "Domain Name System (DNS) Case Insensitivity Clarification" <http://www.rfc-
editor.org/info/rfc4343>
• RFC4380 "Teredo: Tunneling IPv6 over UDP through Network Address Translations (NATs)"
<http://www.rfc-editor.org/info/rfc4380>
• RFC4843 "An IPv6 Prefix for Overlay Routable Cryptographic Hash Identifiers (ORCHID)"
<http://www.rfc-editor.org/info/rfc4843>
• RFC5155 "DNS Security (DNSSEC) Hashed Authenticated Denial of Existence"
<http://www.rfc-editor.org/info/rfc5155>
• RFC5156 "Special-Use IPv6 Addresses" <http://www.rfc-editor.org/info/rfc5156>
• RFC5180 "IPv6 Benchmarking Methodology for Network Interconnect Devices"
<http://www.rfc-editor.org/info/rfc5180>
• RFC5321 "Simple Mail Transfer Protocol" <http://www.rfc-editor.org/info/rfc5321>
• RFC5358 "Preventing Use of Recursive Nameservers in Reflector Attacks"
<http://www.rfc-editor.org/info/rfc5358>
• RFC5737 "IPv4 Address Blocks Reserved for Documentation" <http://www.rfc-
editor.org/info/rfc5737>
• RFC5771 "IANA Guidelines for IPv4 Multicast Address Assignments" <http://www.rfc-
editor.org/info/rfc5771>
• RFC5892 "The Unicode Code Points and Internationalized Domain Names for Applications
(IDNA)" <http://www.rfc-editor.org/info/rfc5892>
• RFC5936 "DNS Zone Transfer Protocol (AXFR)" <http://www.rfc-editor.org/info/rfc5936>
• RFC6052 "IPv6 Addressing of IPv4/IPv6 Translators" <http://www.rfc-
editor.org/info/rfc6052>
• RFC6333 "Dual-Stack Lite Broadband Deployments Following IPv4 Exhaustion"
<http://www.rfc-editor.org/info/rfc6333>
• RFC6598 "IANA-Reserved IPv4 Prefix for Shared Address Space" <http://www.rfc-
editor.org/info/rfc6598>
• RFC6666 "A Discard Prefix for IPv6" <http://www.rfc-editor.org/info/rfc6666>
• RFC6781 "DNSSEC Operational Practices, Version 2" <http://www.rfc-
editor.org/info/rfc6781>
• RFC6890 "Special-Purpose IP Address Registries" <http://www.rfc-
editor.org/info/rfc6890>
• RFC6891 "Extension Mechanisms for DNS (EDNS(0))" <http://www.rfc-
editor.org/info/rfc6891>
• RFC7050 "Discovery of the IPv6 Prefix Used for IPv6 Address Synthesis"
<http://www.rfc-editor.org/info/rfc7050>