Improve RFC links (#8612)

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

View File

@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.miek.nl
.TH "COREFILE" 5 "March 2021" "CoreDNS" "CoreDNS"
.TH "COREFILE" 5 "October 2026" "CoreDNS" "CoreDNS"
.SH "NAME"
.PP
@@ -47,6 +47,21 @@ match on the query name will receive the query.
server with no plugins will just return SERVFAIL for all queries. Each plugin can have a number of
properties than can have arguments, see the documentation for each plugin.
.PP
The Corefile is line oriented: the arguments of a plugin, or of one of its properties, run until the
end of the line. Put each plugin, each property and each closing \fB\fC}\fR on a line of its own. A \fB\fC}\fR that
shares a line with a plugin or a property can be read as part of that line. For example, this fails
with "Unexpected '}' because no matching opening brace":
.PP
.RS
.nf
\&. { whoami }
.fi
.RE
.PP
Comments are allowed and begin with an unquoted hash \fB\fC#\fR and continue to the end of the line.
Comments may be started anywhere on a line.