Mirrors/coredns
1
0
Fork 0
mirror of https://github.com/coredns/coredns.git synced 2026-10-27 04:35:43 -04:00
Code Issues Packages Projects Releases Wiki Activity

Improve RFC links (#8612)

Browse Source 
The `tools.ietf.org` site now redirects to `www.rfc-editor.org`.
* Update various URLs to the new site.
* Make links to `www.rfc-editor.org` consistent.

Signed-off-by: SuperQ <superq@gmail.com>
This commit is contained in:
Ben Kochie
2026-10-08 10:21:06 +02:00
committed by GitHub
parent 763bdb9b76
commit 311a9915da
60 changed files with 1006 additions and 215 deletions
Download Patch File Download Diff File Expand all files Collapse all files

47
man/coredns-file.7
View File

@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.miek.nl
.TH "COREDNS-FILE" 7 "March 2026" "CoreDNS" "CoreDNS Plugins"
.TH "COREDNS-FILE" 7 "October 2026" "CoreDNS" "CoreDNS Plugins"
.SH "NAME"
.PP
@@ -30,6 +30,13 @@ plugin will be prepended to it.
are used.
.PP
The SOA record's owner name must match the zone being loaded. Names without a final dot are
relative to the current origin; for example, \fB\fCtest\fR in a zone loaded as \fB\fCtest.\fR becomes
\fB\fCtest.test.\fR, not \fB\fCtest.\fR. Use \fB\fC@\fR (when the current origin matches the zone) or the zone's
absolute name for the SOA owner. A mismatched SOA causes loading to fail; an invalid reload
leaves the last successfully loaded zone in service.
.PP
If you want to round-robin A and AAAA responses look at the \fIloadbalance\fP plugin.
@@ -39,6 +46,7 @@ If you want to round-robin A and AAAA responses look at the \fIloadbalance\fP pl
.nf
file DBFILE [ZONES... ] {
reload DURATION
reload\_by\_mtime
fallthrough [ZONES...]
}
@@ -50,6 +58,9 @@ file DBFILE [ZONES... ] {
Value of \fB\fC0\fR means to not scan for changes and reload. For example, \fB\fC30s\fR checks the zonefile every 30 seconds
and reloads the zone when serial changes.
.IP \(bu 4
\fB\fCreload_by_mtime\fR if set, decision to reload the zone will be based on the zone file modification time,
instead of change in the SOA serial.
.IP \(bu 4
\fB\fCfallthrough\fR If zone matches and no record can be generated, pass request to the next plugin.
If \fB[ZONES...]\fP is omitted, then fallthrough happens for all zones for which the plugin
is authoritative. If specific zones are listed (for example \fB\fCin-addr.arpa\fR and \fB\fCip6.arpa\fR), then only
@@ -79,8 +90,8 @@ example.org {
.RE
.PP
Where \fB\fCdb.example.org\fR would contain RRSets (https://tools.ietf.org/html/rfc7719#section-4
\[la]https://tools.ietf.org/html/rfc7719#section-4\[ra]) in the
Where \fB\fCdb.example.org\fR would contain RRSets (https://www.rfc-editor.org/info/rfc7719/#section-4
\[la]https://www.rfc-editor.org/info/rfc7719/#section-4\[ra]) in the
(text) presentation format from RFC 1035:
.PP
@@ -99,14 +110,14 @@ www IN A 127.0.0.1
.RE
.PP
Or use a single zone file for multiple zones:
Or use a single zone file for multiple zones, with relative owner names and no fixed \fB\fC$ORIGIN\fR:
.PP
.RS
.nf
\&. {
file example.org.signed example.org example.net
file db.shared example.org example.net
transfer example.org example.net {
to * 10.240.1.1
}
@@ -115,6 +126,24 @@ Or use a single zone file for multiple zones:
.fi
.RE
.PP
For example, \fB\fCdb.shared\fR can contain:
.PP
.RS
.nf
@ 3600 IN SOA sns.dns.icann.org. noc.dns.icann.org. 2017042745 7200 3600 1209600 3600
@ 3600 IN NS a.iana\-servers.net.
www 3600 IN A 127.0.0.1
.fi
.RE
.PP
Each configured zone is used as the initial origin when parsing this file, so \fB\fC@\fR is its apex.
Signed zones require signatures for the actual owner names and must be signed separately.
.PP
Note that if you have a configuration like the following you may run into a problem of the origin
not being correctly recognized:
@@ -132,9 +161,9 @@ not being correctly recognized:
.PP
We omit the origin for the file \fB\fCdb.example.org\fR, so this references the zone in the server block,
which, in this case, is the root zone. Any contents of \fB\fCdb.example.org\fR 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:
which, in this case, is the root zone. A file with an SOA for \fB\fCexample.org.\fR will be rejected
because it does not match the configured root zone, even if the file sets \fB\fC$ORIGIN example.org.\fR.
Specify the correct zone in one of two ways:
.PP
.RS
@@ -168,6 +197,6 @@ transfers. Lastly the \fIroot\fP plugin can help you specify the location of the
.PP
See RFC 1035
\[la]https://www.rfc-editor.org/rfc/rfc1035.txt\[ra] for more info on how to structure zone
\[la]https://www.rfc-editor.org/info/rfc1035/\[ra] for more info on how to structure zone
files.