* mw/kubernetes: remove federation and cidr Remove both as we have a corefile syntax change that handles cidr and remove federation because that is going to be its own middleware. * backwards incompat changes This PR: * removes cidr from kubernetes (core Corefile feature now) * removes federation from kubernets (comes back as new middleware) * [remove autopath - which was already gone, so that already was backwards incompat] * adds `fallthrough` to the *etcd* middleware and makes you enable it. * Fail on unknown properties * documentation * Disable TestHealthCheck as it uses realtime and fails |
||
---|---|---|
.. | ||
erratic.go | ||
erratic_test.go | ||
README.md | ||
setup.go | ||
setup_test.go |
erratic
erratic is a middleware useful for testing client behavior. It returns a static response to all queries, but the responses can be delayed, dropped or truncated.
The erratic middleware will respond to every A or AAAA query. For any other type it will return a SERVFAIL response. The reply for A will return 192.0.2.53 (see RFC 5737), for AAAA it returns 2001:DB8::53 (see RFC 3849).
Syntax
erratic {
drop [AMOUNT]
truncate [AMOUNT]
delay [AMOUNT [DURATION]]
}
drop
: drop 1 per AMOUNT of queries, the default is 2.truncate
: truncate 1 per AMOUNT of queries, the default is 2.delay
: delay 1 per AMOUNT of queries for DURATION, the default for AMOUNT is 2 and the default for DURATION is 100ms.
Examples
.:53 {
erratic {
drop 3
}
}
Or even shorter if the defaults suits you. Note this only drops queries, it does not delay them.
. {
erratic
}
Delay 1 in 3 queries for 50ms
. {
erratic {
delay 3 50ms
}
}
Delay 1 in 3 and truncate 1 in 5.
. {
erratic {
delay 3 5ms
truncate 5
}
}
Drop every second query.
. {
erratic {
drop 2
truncate 2
}
}