You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: cmd/routedns/config.go
+2-1Lines changed: 2 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -109,8 +109,9 @@ type group struct {
109
109
EDNS0Data []byte`toml:"edns0-data"`// EDNS0 modifier option data
110
110
111
111
// Failover/Failback options
112
-
ResetAfterint`toml:"reset-after"`// Time in seconds after which to reset resolvers in fail-back and random groups, default 60.
112
+
ResetAfter*int`toml:"reset-after"`// Time in seconds after which to reset resolvers in fail-back and random groups, or 0 to reset immediately, default 60.
113
113
ServfailErrorbool`toml:"servfail-error"`// If true, SERVFAIL responses are considered errors and cause failover etc.
114
+
EmptyErrorbool`toml:"empty-error"`// If true, empty responses are considered errors and cause failover etc.
Copy file name to clipboardExpand all lines: doc/configuration.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -519,6 +519,7 @@ Options:
519
519
520
520
-`resolvers` - An array of upstream resolvers or modifiers.
521
521
-`servfail-error` - If `true`, a SERVFAIL response from an upstream resolver is considered a failure triggering a switch to the next resolver. This can happen when DNSSEC validation fails for example. Default `false`.
522
+
-`empty-error` - If `true`, an empty reponse from an upstream resolver is considered a failure triggering a switch to the next resolver. Default `false`.
522
523
523
524
#### Examples
524
525
@@ -539,8 +540,9 @@ Fail-Back groups are instantiated with `type = "fail-back"` in the groups sectio
539
540
Options:
540
541
541
542
-`resolvers` - An array of upstream resolvers or modifiers. The first in the array is the preferred resolver.
542
-
-`reset-after` - Time in seconds before switching from an alternative resolver back to the preferred resolver (first in the list), default 60. Note: This is not a timeout argument. After a failure of the preferred resolver, this defines the amount of time to use alternative/failover resolvers before switching back to the preferred. You can have as many resolvers in the array as the time limit allows.
543
+
-`reset-after` - Non-zero time in seconds before switching from an alternative resolver back to the preferred resolver (first in the list), or a negative number to switch back immediately, default 60. Note: This is not a timeout argument. After a failure of the preferred resolver, this defines the amount of time to use alternative/failover resolvers before switching back to the preferred. You can have as many resolvers in the array as the time limit allows.
543
544
-`servfail-error` - If `true`, a SERVFAIL response from an upstream resolver is considered a failure triggering a failover. This can happen when DNSSEC validation fails for example. Default `false`.
545
+
-`empty-error` - If `true`, an empty reponse from an upstream resolver is considered a failure triggering a switch to the next resolver. Default `false`.
544
546
545
547
#### Examples
546
548
@@ -561,8 +563,9 @@ Random groups are instantiated with `type = "random"` in the groups section of t
561
563
Options:
562
564
563
565
-`resolvers` - An array of upstream resolvers or modifiers.
564
-
-`reset-after` - Time in seconds to disable a failed resolver, default 60.
566
+
-`reset-after` - Non-zero time in seconds to disable a failed resolver, or a negative number to disable only for a single request, default 60.
565
567
-`servfail-error` - If `true`, a SERVFAIL response from an upstream resolver is considered a failure which will take the resolver temporarily out of the group. This can happen when DNSSEC validation fails for example. Default `false`.
568
+
-`empty-error` - If `true`, an empty reponse from an upstream resolver is considered a failure triggering a switch to the next resolver. Default `false`.
0 commit comments