Mirrors/coredns
1
0
Fork 0
mirror of https://github.com/coredns/coredns.git synced 2026-06-02 07:10:24 -04:00
Code Issues Packages Projects Releases Wiki Activity

plugin/forward: Forward NODATA responses to Next handler (#8065)

Browse Source
This commit is contained in:
Jöran Malek
2026-05-27 02:15:46 +02:00
committed by GitHub
parent 17142359e0
commit eb49f402cc
4 changed files with 109 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
plugin/forward/README.md
View File

@@ -111,6 +111,7 @@ forward FROM TO... {
at least greater than the expected *upstream query rate* * *latency* of the upstream servers.
As an upper bound for **MAX**, consider that each concurrent query will use about 2kb of memory.
* `next` If the `RCODE` (i.e. `NXDOMAIN`) is returned by the remote then execute the next plugin. If no next plugin is defined, or the next plugin is not a `forward` plugin, this setting is ignored
* `next_on_nodata` If `NOERROR` is returned by the remote, but an empty answer section (`NODATA`) was provided, execute the next `forward` plugin, if configured.
* `failfast_all_unhealthy_upstreams` - determines the handling of requests when all upstream servers are unhealthy and unresponsive to health checks. Enabling this option will immediately return SERVFAIL responses for all requests. By default, requests are sent to a random upstream.
* `failover` - By default when a DNS lookup fails to return a DNS response (e.g. timeout), _forward_ will attempt a lookup on the next upstream server. The `failover` option will make _forward_ do the same for any response with a response code matching an `RCODE` ( e.g. `SERVFAIL`、`REFUSED`). `NOERROR` cannot be used. If all upstreams have been tried, the response from the last attempt is returned.