Mirrors/coredns
1
0
Fork 0
mirror of https://github.com/coredns/coredns.git synced 2026-10-12 13:35:21 -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

4
plugin/any/README.md
View File

@@ -8,7 +8,7 @@
## Description
*any* basically blocks ANY queries by responding to them with a short HINFO reply. See [RFC
8482](https://tools.ietf.org/html/rfc8482) for details.
8482](https://www.rfc-editor.org/info/rfc8482/) for details.
## Syntax
@@ -33,4 +33,4 @@ example.org. 8482 IN HINFO "ANY obsoleted" "See RFC 8482"
## See Also
[RFC 8482](https://tools.ietf.org/html/rfc8482).
[RFC 8482](https://www.rfc-editor.org/info/rfc8482/).

2
plugin/bufsize/README.md
View File

@@ -9,7 +9,7 @@ of the request will be reduced. Otherwise the request is unaffected.
It prevents IP fragmentation, mitigating certain DNS vulnerabilities.
It cannot increase UDP size requested by the client, it can be reduced only.
This will only affect queries that have
an OPT RR ([EDNS(0)](https://www.rfc-editor.org/rfc/rfc6891)).
an OPT RR ([EDNS(0)](https://www.rfc-editor.org/info/rfc6891/)).
## Syntax
```txt

4
plugin/dns64/README.md
View File

@@ -99,8 +99,8 @@ Not all features required by DNS64 are implemented, only basic AAAA synthesis.
* Support "mapping of separate IPv4 ranges to separate IPv6 prefixes"
* Resolve PTR records
* Make resolver DNSSEC aware. See: [RFC 6147 Section 3](https://tools.ietf.org/html/rfc6147#section-3)
* Make resolver DNSSEC aware. See: [RFC 6147 Section 3](https://www.rfc-editor.org/info/rfc6147/#section-3)
## See Also
See [RFC 6147](https://tools.ietf.org/html/rfc6147) for more information on the DNS64 mechanism.
See [RFC 6147](https://www.rfc-editor.org/info/rfc6147/) for more information on the DNS64 mechanism.

2
plugin/dns64/dns64.go
View File

@@ -1,6 +1,6 @@
// Package dns64 implements a plugin that performs DNS64.
//
// See: RFC 6147 (https://tools.ietf.org/html/rfc6147)
// See: RFC 6147 (https://www.rfc-editor.org/info/rfc6147/)
package dns64
import (

2
plugin/dnssec/black_lies.go
View File

@@ -10,7 +10,7 @@ import (
)
// nsec returns an NSEC useful for NXDOMAIN responses.
// See https://tools.ietf.org/html/draft-valsorda-dnsop-black-lies-00
// See https://datatracker.ietf.org/doc/html/draft-valsorda-dnsop-black-lies-00
// For example, a request for the non-existing name a.example.com would
// cause the following NSEC record to be generated:
//

4
plugin/dynupdate/README.md
View File

@@ -248,6 +248,6 @@ updated zones, not a high-throughput DHCP service.
See the *file*, *transfer*, and *tsig* plugins for authoritative data,
AXFR/NOTIFY, and TSIG authentication configuration.
* [RFC 2136](https://www.rfc-editor.org/rfc/rfc2136) defines DNS UPDATE.
* [RFC 1982](https://www.rfc-editor.org/rfc/rfc1982) defines DNS serial
* [RFC 2136](https://www.rfc-editor.org/info/rfc2136/) defines DNS UPDATE.
* [RFC 1982](https://www.rfc-editor.org/info/rfc1982/) defines DNS serial
number arithmetic.

6
plugin/erratic/README.md
View File

@@ -9,8 +9,8 @@
*erratic* returns a static response to all queries, but the responses can be delayed,
dropped or truncated. The *erratic* plugin will respond to every A or AAAA query. For
any other type it will return a SERVFAIL response (except AXFR). The reply for A will return
192.0.2.53 ([RFC 5737](https://tools.ietf.org/html/rfc5737)), for AAAA it returns 2001:DB8::53 ([RFC
3849](https://tools.ietf.org/html/rfc3849)). For an AXFR request it will respond with a small
192.0.2.53 ([RFC 5737](https://www.rfc-editor.org/info/rfc5737/)), for AAAA it returns 2001:DB8::53 ([RFC
3849](https://www.rfc-editor.org/info/rfc3849/)). For an AXFR request it will respond with a small
zone transfer.
## Syntax
@@ -86,4 +86,4 @@ example.org {
## See Also
[RFC 3849](https://tools.ietf.org/html/rfc3849) and [RFC 5737](https://tools.ietf.org/html/rfc5737).
[RFC 3849](https://www.rfc-editor.org/info/rfc3849/) and [RFC 5737](https://www.rfc-editor.org/info/rfc5737/).

4
plugin/file/README.md
View File

@@ -64,7 +64,7 @@ example.org {
}
~~~
Where `db.example.org` would contain RRSets (<https://tools.ietf.org/html/rfc7719#section-4>) in the
Where `db.example.org` would contain RRSets (<https://www.rfc-editor.org/info/rfc7719/#section-4>) in the
(text) presentation format from RFC 1035:
~~~
@@ -133,5 +133,5 @@ example.org {
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](https://www.rfc-editor.org/rfc/rfc1035.txt) for more info on how to structure zone
See [RFC 1035](https://www.rfc-editor.org/info/rfc1035/) for more info on how to structure zone
files.

6
plugin/forward/README.md
View File

@@ -382,8 +382,8 @@ Forward to an upstream identified by hostname, using a specific resolver to look
## See Also
[RFC 7858](https://tools.ietf.org/html/rfc7858) for DNS over TLS.
[RFC 7858](https://www.rfc-editor.org/info/rfc7858/) for DNS over TLS.
[RFC 8484](https://tools.ietf.org/html/rfc8484) for DNS over HTTPS.
[RFC 8484](https://www.rfc-editor.org/info/rfc8484/) for DNS over HTTPS.
[RFC 9250](https://www.rfc-editor.org/rfc/rfc9250.html) for DNS over QUIC.
[RFC 9250](https://www.rfc-editor.org/info/rfc9250/) for DNS over QUIC.

2
plugin/geoip/README.md
View File

@@ -89,7 +89,7 @@ geoip [DBFILE] {
**NOTE:** due to security reasons, recursive DNS resolvers may mask a few bits off of the clients' IP address, which can cause inaccuracies in GeoIP resolution.
There is no defined mask size in the standards, but there are examples: [RFC 7871's example](https://datatracker.ietf.org/doc/html/rfc7871#section-13) conceals the last 72 bits of an IPv6 source address, and NS1 Help Center [mentions](https://help.ns1.com/hc/en-us/articles/360020256573-About-the-EDNS-Client-Subnet-ECS-DNS-extension) that ECS-enabled DNS resolvers send only the first three octets (eg. /24) of the source IPv4 address.
There is no defined mask size in the standards, but there are examples: [RFC 7871's example](https://www.rfc-editor.org/info/rfc7871/#section-13) conceals the last 72 bits of an IPv6 source address, and NS1 Help Center [mentions](https://help.ns1.com/hc/en-us/articles/360020256573-About-the-EDNS-Client-Subnet-ECS-DNS-extension) that ECS-enabled DNS resolvers send only the first three octets (eg. /24) of the source IPv4 address.
## Examples

2
plugin/hosts/README.md
View File

@@ -165,4 +165,4 @@ exceptions, and fall through for everything else under `example.com`.
## See also
The form of the entries in the `/etc/hosts` file are based on IETF [RFC 952](https://tools.ietf.org/html/rfc952) which was updated by IETF [RFC 1123](https://tools.ietf.org/html/rfc1123).
The form of the entries in the `/etc/hosts` file are based on IETF [RFC 952](https://www.rfc-editor.org/info/rfc952/) which was updated by IETF [RFC 1123](https://www.rfc-editor.org/info/rfc1123/).

4
plugin/hosts/hostsfile_test.go
View File

@@ -49,7 +49,7 @@ var (
123.123.123 loki
321.321.321.321`
singlelinehosts = `127.0.0.2 odin`
ipv4hosts = `# See https://tools.ietf.org/html/rfc1123.
ipv4hosts = `# See https://www.rfc-editor.org/info/rfc1123/.
#
# internet address and host name
@@ -58,7 +58,7 @@ var (
# internet address, host name and aliases
127.0.0.3 localhost localhost.localdomain`
ipv6hosts = `# See https://tools.ietf.org/html/rfc5952, https://tools.ietf.org/html/rfc4007.
ipv6hosts = `# See https://www.rfc-editor.org/info/rfc5952/, https://www.rfc-editor.org/info/rfc4007/.
# internet address and host name
::1 localhost # inline comment separated by tab

4
plugin/nsid/README.md
View File

@@ -6,7 +6,7 @@
## Description
This plugin implements [RFC 5001](https://tools.ietf.org/html/rfc5001) and adds an EDNS0 OPT
This plugin implements [RFC 5001](https://www.rfc-editor.org/info/rfc5001/) and adds an EDNS0 OPT
resource record to replies that uniquely identify the server. This is useful in anycast setups to
see which server was responsible for generating the reply and for debugging.
@@ -54,4 +54,4 @@ And now a client with NSID support will see an OPT record with the NSID option:
## See Also
[RFC 5001](https://tools.ietf.org/html/rfc5001)
[RFC 5001](https://www.rfc-editor.org/info/rfc5001/)

6
plugin/siit/README.md
View File

@@ -48,12 +48,12 @@ The `server` label is explained in the _prometheus_ plugin documentation.
## Bugs
* Prefix matching in eam is not implemented yet.
* DNSSEC support is not implemented yet. The problem is the same as DNS64. See: [RFC 6147 Section 3](https://tools.ietf.org/html/rfc6147#section-3)
* DNSSEC support is not implemented yet. The problem is the same as DNS64. See: [RFC 6147 Section 3](https://www.rfc-editor.org/info/rfc6147/#section-3)
## See Also
See [RFC 6052](https://tools.ietf.org/html/rfc6052) for more information on the SIIT mechanism
and [RFC 7757](https://tools.ietf.org/html/rfc7757) about the explicit address mappings (eam) mechanism
See [RFC 6052](https://www.rfc-editor.org/info/rfc6052/) for more information on the SIIT mechanism
and [RFC 7757](https://www.rfc-editor.org/info/rfc7757/) about the explicit address mappings (eam) mechanism
## Notes

4
plugin/siit/siit.go
View File

@@ -1,7 +1,7 @@
// Package siit implements a plugin that performs AAAA to A translation.
//
// See: RFC 6052 (https://tools.ietf.org/html/rfc6052)
// See: RFC 7757 (https://tools.ietf.org/html/rfc7757)
// See: RFC 6052 (https://www.rfc-editor.org/info/rfc6052/)
// See: RFC 7757 (https://www.rfc-editor.org/info/rfc7757/)
package siit
import (

8
plugin/template/README.md
View File

@@ -30,7 +30,7 @@ template CLASS TYPE [ZONE...] {
* `match` **REGEX** [Go regexp](https://golang.org/pkg/regexp/) that are matched against the incoming question name.
Specifying no regex matches everything (default: `.*`). First matching regex wins. Regex patterns
must not exceed 10000 characters.
* `answer|additional|authority` **RR** A [RFC 1035](https://tools.ietf.org/html/rfc1035#section-5) style resource record fragment
* `answer|additional|authority` **RR** A [RFC 1035](https://www.rfc-editor.org/info/rfc1035/#section-5) style resource record fragment
built by a [Go template](https://golang.org/pkg/text/template/) that contains the reply. Specifying no answer will result
in a response with an empty answer section.
* `var` **NAME** **EXPRESSION** sets the variable **NAME** to the result of **EXPRESSION**, evaluated for each matching query
@@ -71,7 +71,7 @@ and the following predefined [template functions](https://golang.org/pkg/text/te
* `parseInt` interprets a string in the given base and bit size. Equivalent to [strconv.ParseUint](https://golang.org/pkg/strconv#ParseUint).
The output of the template must be a [RFC 1035](https://tools.ietf.org/html/rfc1035) style resource record (commonly referred to as a "zone file").
The output of the template must be a [RFC 1035](https://www.rfc-editor.org/info/rfc1035/) style resource record (commonly referred to as a "zone file").
**WARNING** there is a syntactical problem with Go templates and CoreDNS config files. Expressions
like `{{$var}}` will be interpreted as a reference to an environment variable by CoreDNS (and
@@ -123,7 +123,7 @@ The most simplistic template is
### Resolve .invalid as NXDOMAIN
The `.invalid` domain is a reserved TLD (see [RFC 2606 Reserved Top Level DNS Names](https://tools.ietf.org/html/rfc2606#section-2)) to indicate invalid domains.
The `.invalid` domain is a reserved TLD (see [RFC 2606 Reserved Top Level DNS Names](https://www.rfc-editor.org/info/rfc2606/#section-2)) to indicate invalid domains.
~~~ corefile
. {
@@ -342,7 +342,7 @@ requested type.
* [Go regexp](https://golang.org/pkg/regexp/) for details about the regex implementation
* [RE2 syntax reference](https://github.com/google/re2/wiki/Syntax) for details about the regex syntax
* [RFC 1034](https://tools.ietf.org/html/rfc1034#section-3.6.1) and [RFC 1035](https://tools.ietf.org/html/rfc1035#section-5) for the resource record format
* [RFC 1034](https://www.rfc-editor.org/info/rfc1034/#section-3.6.1) and [RFC 1035](https://www.rfc-editor.org/info/rfc1035/#section-5) for the resource record format
* [Go template](https://golang.org/pkg/text/template/) for the template language reference
## Bugs

2
plugin/tls/README.md
View File

@@ -128,4 +128,4 @@ debugging these transports harder than it should be.
## See Also
RFC 7858 and https://grpc.io.
[RFC 7858](https://www.rfc-editor.org/info/rfc7858/) and https://grpc.io.

2
plugin/tsig/README.md
View File

@@ -101,7 +101,7 @@ With the *transfer* plugin, zone transfer notifications from CoreDNS are not TSI
### Special Considerations for Forwarding Servers (RFC 8945 5.5)
https://datatracker.ietf.org/doc/html/rfc8945#section-5.5
https://www.rfc-editor.org/info/rfc8945/#section-5.5
CoreDNS does not implement this section as follows ...