Mirrors/coredns
1
0
Fork 0
mirror of https://github.com/coredns/coredns.git synced 2025-12-08 19:35:10 -05:00
Code Issues Packages Projects Releases Wiki Activity

auto make -f Makefile.doc

Browse Source
This commit is contained in:
coredns-auto-go-mod-tidy[bot]
2020-04-23 08:22:49 +00:00
parent ec5696b202
commit aa75e0c295
47 changed files with 95 additions and 74 deletions
Download Patch File Download Diff File Expand all files Collapse all files

75
man/coredns-dns64.7
View File

@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.miek.nl
.TH "COREDNS-DNS64" 7 "March 2020" "CoreDNS" "CoreDNS Plugins"
.TH "COREDNS-DNS64" 7 "April 2020" "CoreDNS" "CoreDNS Plugins"
.SH "NAME"
.PP
@@ -7,52 +7,62 @@
.SH "DESCRIPTION"
.PP
.RS
The \fIdns64\fP plugin will when asked for a domain's AAAA records, but only finds A records,
synthesizes the AAAA records from the A records.
.PP
DNS64 describes a DNS server that when asked for a domain's AAAA records, but only finds
A records, synthesizes the AAAA records from the A records.
.RE
.PP
The synthesis in only performed if the query came in via IPv6.
The synthesis is \fIonly\fP performed \fBif the query came in via IPv6\fP.
.PP
This translation is for IPv6-only networks that have NAT64
\[la]https://en.wikipedia.org/wiki/NAT64\[ra].
.PP
See RFC 6147
\[la]https://tools.ietf.org/html/rfc6147\[ra] for more information.
.SH "SYNTAX"
.PP
.RS
.nf
dns64 [PREFIX]
.fi
.RE
.IP \(bu 4
\fBPREFIX\fP defines a custom prefix instead of the default \fB\fC64:ff9b::/96\fR.
.PP
Or use this slightly longer form with more options:
.PP
.RS
.nf
dns64 [PREFIX] {
[translate\_all]
[translate\_all]
prefix PREFIX
}
.fi
.RE
.IP \(bu 4
[PREFIX] defines a custom prefix instead of the default \fB\fC64:ff9b::/96\fR.
\fB\fCprefix\fR specifies any local IPv6 prefix to use, instead of the well known prefix (64:ff9b::/96)
.IP \(bu 4
\fB\fCtranslate_all\fR translates all queries, including respones that have AAAA results.
\fB\fCtranslate_all\fR translates all queries, including responses that have AAAA results.
.SH "EXAMPLES"
.PP
Translate with the default well known prefix. Applies to all queries.
Translate with the default well known prefix. Applies to all queries (if they came in over IPv6).
.PP
.RS
.nf
dns64
\&. {
dns64
}
.fi
.RE
@@ -64,9 +74,17 @@ Use a custom prefix.
.RS
.nf
dns64 64:1337::/96
dns64 {
prefix 64:1337::/96
\&. {
dns64 64:1337::/96
}
~~~~
Or
~~~ corefile
\&. {
dns64 {
prefix 64:1337::/96
}
}
.fi
@@ -79,17 +97,15 @@ Enable translation even if an existing AAAA record is present.
.RS
.nf
dns64 {
translate\_all
\&. {
dns64 {
translate\_all
}
}
.fi
.RE
.IP \(bu 4
\fB\fCprefix\fR specifies any local IPv6 prefix to use, instead of the well known prefix (64:ff9b::/96)
.SH "METRICS"
.PP
If monitoring is enabled (via the \fIprometheus\fP plugin) then the following metrics are exported:
@@ -116,3 +132,8 @@ Make resolver DNSSEC aware. See: RFC 6147 Section 3
\[la]https://tools.ietf.org/html/rfc6147#section-3\[ra]
.SH "ALSO SEE"
.PP
See RFC 6147
\[la]https://tools.ietf.org/html/rfc6147\[ra] for more information on the DNS64 mechanism.