named-rrchecker - syntax checker for individual DNS resource
records
named-rrchecker [-h] [-o origin] [-p]
[-u] [-C] [-T] [-P]
named-rrchecker reads a single DNS resource record (RR)
from standard input and checks whether it is syntactically correct.
- Input must not start with an owner (domain) name
- The CLASS field is mandatory (typically IN).
- The TTL field must not be present.
- RDATA format is specific to each RRTYPE.
- Leading and trailing whitespace in each field is ignored.
Format details can be found in RFC 1035 Section 5.1 under
<rr> specification. RFC 3597 format is also accepted in
any of the input fields. See Examples.
- -o origin
- This option specifies the origin to be used when interpreting names in the
record: it defaults to root (.). The specified origin is always
taken as an absolute name.
- -p
- This option prints out the resulting record in canonical form. If there is
no canonical form defined, the record is printed in RFC 3597
unknown record format.
- -u
- This option prints out the resulting record in RFC 3597 unknown
record format.
- -C, -T, -P
- These options do not read input. They print out known classes, standard
types, and private type mnemonics. Each item is printed on a separate
line. The resulting list of private types may be empty
- -h
- This option prints out the help menu.
Pay close attention to the echo command line options
-e and -n, as they affect whitespace in the input to
named-rrchecker.
Special characters allowed in zone files by RFC 1035 Section
5.1 are accepted.
For multi-line examples see the next section.
- 0
- The whole input was parsed as one syntactically valid resource
record.
- 1
- The input is not a syntactically valid resource record, or the given type
is not supported, or either/both class and type are meta-values, which
should not appear in zone files.
RFC 1034, RFC 1035, RFC 3957,
named(8).
Internet Systems Consortium
2025, Internet Systems Consortium