5f41d8eb1f
Make normalize return multiple "hosts" (= reverse zones) when a non-octet boundary cidr is given. Added pkg/cidr package that holds the cidr calculation routines; felt they didn't really fit dnsutil. This change means the IPNet return parameter isn't needed, the hosts are all correct. The tests that tests this is also removed: TestSplitHostPortReverse The fallout was that zoneAddr _also_ doesn't need the IPNet member, that in turn make it visible that zoneAddr in address.go duplicated a bunch of stuff from register.go; removed/refactored that too. Created a plugin.OriginsFromArgsOrServerBlock to help plugins do the right things, by consuming ZONE arguments; this now expands reverse zones correctly. This is mostly mechanical. Remove the reverse test in plugin/kubernetes which is a copy-paste from a core test (which has since been fixed). Remove MustNormalize as it has no plugin users. This change is not backwards compatible to plugins that have a ZONE argument that they parse in the setup util. All in-tree plugins have been updated. Signed-off-by: Miek Gieben <miek@miek.nl>
file
Name
file - enables serving zone data from an RFC 1035-style master file.
Description
The file plugin is used for an "old-style" DNS server. It serves from a preloaded file that exists on disk contained RFC 1035 styled data. If the zone file contains signatures (i.e., is signed using DNSSEC), correct DNSSEC answers are returned. Only NSEC is supported! If you use this setup you are responsible for re-signing the zonefile.
Syntax
file DBFILE [ZONES...]
- DBFILE the database file to read and parse. If the path is relative, the path from the root plugin will be prepended to it.
- ZONES zones it should be authoritative for. If empty, the zones from the configuration block are used.
If you want to round-robin A and AAAA responses look at the loadbalance plugin.
file DBFILE [ZONES... ] {
reload DURATION
}
reloadinterval to perform a reload of the zone if the SOA version changes. Default is one minute. Value of0means to not scan for changes and reload. For example,30schecks the zonefile every 30 seconds and reloads the zone when serial changes.
If you need outgoing zone transfers, take a look at the transfer plugin.
Examples
Load the example.org zone from db.example.org and allow transfers to the internet, but send
notifies to 10.240.1.1
example.org {
file db.example.org
transfer {
to * 10.240.1.1
}
}
Where db.example.org would contain RRSets (https://tools.ietf.org/html/rfc7719#section-4) in the
(text) presentation format from RFC 1035:
$ORIGIN example.org.
@ 3600 IN SOA sns.dns.icann.org. noc.dns.icann.org. 2017042745 7200 3600 1209600 3600
3600 IN NS a.iana-servers.net.
3600 IN NS b.iana-servers.net.
www IN A 127.0.0.1
IN AAAA ::1
Or use a single zone file for multiple zones:
. {
file example.org.signed example.org example.net
transfer example.org example.net {
to * 10.240.1.1
}
}
Note that if you have a configuration like the following you may run into a problem of the origin not being correctly recognized:
. {
file db.example.org
}
We omit the origin for the file db.example.org, so this references the zone in the server block,
which, in this case, is the root zone. Any contents of db.example.org will then read with that
origin set; this may or may not do what you want.
It's better to be explicit here and specify the correct origin. This can be done in two ways:
. {
file db.example.org example.org
}
Or
example.org {
file db.example.org
}
See Also
See the loadbalance plugin if you need simple record shuffling. And the transfer plugin for zone transfers. Lastly the root plugin can help you specify the location of the zone files.
See RFC 1035 for more info on how to structure zone files.