chore(docs): regenerate man pages (#7971)

man/coredns-dns64.7

@@ -1,5 +1,5 @@
 .\" Generated by Mmark Markdown Processer - mmark.miek.nl
-.TH "COREDNS-DNS64" 7 "March 2021" "CoreDNS" "CoreDNS Plugins"
+.TH "COREDNS-DNS64" 7 "March 2026" "CoreDNS" "CoreDNS Plugins"
 
 .SH "NAME"
 .PP
@@ -41,6 +41,7 @@ Or use this slightly longer form with more options:
 dns64 [PREFIX] {
     [translate\_all]
     prefix PREFIX
+    [allow\_ipv4]
 }
 
 .fi
@@ -50,6 +51,8 @@ dns64 [PREFIX] {
 \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 responses that have AAAA results.
+.IP \(bu 4
+\fB\fCallow_ipv4\fR Allow translating queries if they come in over IPv4, default is IPv6 only translation.
 
 
 .SH "EXAMPLES"
@@ -113,6 +116,25 @@ Enable translation even if an existing AAAA record is present.
 .fi
 .RE
 
+.PP
+Apply translation even to the requests which arrived over IPv4 network. Warning, the \fB\fCallow_ipv4\fR feature will apply
+translations to requests coming from dual-stack clients. This means that a request for a client that sends an \fB\fCAAAA\fR
+that would normal result in an \fB\fCNXDOMAIN\fR would get a translated result.
+This may cause unwanted IPv6 dns64 traffic when a dualstack client would normally use the result of an \fB\fCA\fR record request.
+
+.PP
+.RS
+
+.nf
+\&. {
+    dns64 {
+        allow\_ipv4
+    }
+}
+
+.fi
+.RE
+
 .SH "METRICS"
 .PP
 If monitoring is enabled (via the \fIprometheus\fP plugin) then the following metrics are exported: