diff options
| author |  Chris O'Haver <cohaver@infoblox.com>
| 2018-10-22 13:30:42 -0400 |
|---|---|---|
| committer |  Miek Gieben <miek@miek.nl>
| 2018-10-22 18:30:42 +0100 |
| commit | 85e5ab77d65d224e2c2e5a31e28f17595fea6848 (patch) | |
| tree | 17d6220aa8cde69a85bcc56ce1747fc04135d9ca /plugin | |
| parent | 6539a10a62d9f6fa9119335928cf205aba93ec5d (diff) | |
| download | coredns-85e5ab77d65d224e2c2e5a31e28f17595fea6848.tar.gz coredns-85e5ab77d65d224e2c2e5a31e28f17595fea6848.tar.zst coredns-85e5ab77d65d224e2c2e5a31e28f17595fea6848.zip | |
add ipv6 loopback example (#2223)
Diffstat (limited to 'plugin')
| -rw-r--r-- | plugin/loop/README.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/plugin/loop/README.md b/plugin/loop/README.md index 74b749ecd..9bc51be49 100644 --- a/plugin/loop/README.md +++ b/plugin/loop/README.md @@ -55,7 +55,7 @@ memory and CPU until eventual out of memory death by the host. A forwarding loop is usually caused by: -* Most commonly, CoreDNS forwarding requests directly to itself. e.g. to `127.0.0.1` or `127.0.0.53` +* Most commonly, CoreDNS forwarding requests directly to itself. e.g. via a loopback address such as `127.0.0.1`, `::1` or `127.0.0.53` * Less commonly, CoreDNS forwarding to an upstream server that in turn, forwards requests back to CoreDNS. To troubleshoot this problem, look in your Corefile for any `proxy` or `forward` to the zone |