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

man/coredns-grpc.7

@@ -1,5 +1,5 @@
 .\" Generated by Mmark Markdown Processer - mmark.miek.nl
-.TH "COREDNS-GRPC" 7 "March 2021" "CoreDNS" "CoreDNS Plugins"
+.TH "COREDNS-GRPC" 7 "March 2026" "CoreDNS" "CoreDNS Plugins"
 
 .SH "NAME"
 .PP
@@ -48,6 +48,7 @@ grpc FROM TO... {
     tls CERT KEY CA
     tls\_servername NAME
     policy random|round\_robin|sequential
+    fallthrough [ZONES...]
 }
 
 .fi
@@ -82,6 +83,13 @@ but they have to use the same \fB\fCtls_servername\fR. E.g. mixing 9.9.9.9 (Quad
 (Cloudflare) will not work.
 .IP \(bu 4
 \fB\fCpolicy\fR specifies the policy to use for selecting upstream servers. The default is \fB\fCrandom\fR.
+.IP \(bu 4
+\fB\fCfallthrough\fR \fB[ZONES...]\fP If a query results in NXDOMAIN from the gRPC backend, pass the request
+to the next plugin instead of returning the NXDOMAIN response. This is useful when the gRPC backend
+is authoritative for a zone but should not return authoritative NXDOMAIN responses for queries that
+don't actually belong to that zone (e.g., search path queries). If \fB[ZONES...]\fP is omitted, then
+fallthrough happens for all zones. If specific zones are listed, then only queries for those zones
+will be subject to fallthrough.
 
 
 .PP
@@ -198,6 +206,37 @@ Or with multiple upstreams from the same provider
 .fi
 .RE
 
+.PP
+Forward requests to a local upstream listening on a Unix domain socket.
+
+.PP
+.RS
+
+.nf
+\&. {
+    grpc . unix:///path/to/grpc.sock
+}
+
+.fi
+.RE
+
+.PP
+Proxy requests for \fB\fCexample.org.\fR to a gRPC backend, but fallthrough to the next plugin for NXDOMAIN responses to handle search path queries correctly.
+
+.PP
+.RS
+
+.nf
+example.org {
+    grpc . 127.0.0.1:9005 {
+        fallthrough
+    }
+    forward . 8.8.8.8
+}
+
+.fi
+.RE
+
 .SH "BUGS"
 .PP
 The TLS config is global for the whole grpc proxy if you need a different \fB\fCtls_servername\fR for