diff options
| -rw-r--r-- | plugin/loop/README.md | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/plugin/loop/README.md b/plugin/loop/README.md index 5b0a95bda..74b749ecd 100644 --- a/plugin/loop/README.md +++ b/plugin/loop/README.md @@ -54,6 +54,7 @@ DNS servers. This is a fatal error because operating with an infinite loop will 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` * Less commonly, CoreDNS forwarding to an upstream server that in turn, forwards requests back to CoreDNS. @@ -75,9 +76,10 @@ to proxy/forward requests to. Since it contains a local address, CoreDNS ends u requests to itself. There are many ways to work around this issue, some are listed here: + * Add the following to `kubelet`: `--resolv-conf /run/systemd/resolve/resolv.conf`. This flag tells `kubelet` to pass an alternate `resolv.conf` to Pods. For `systemd-resolved`, `/run/systemd/resolve/resolv.conf` is typically the location of the "original" `/etc/resolv.conf`. * Disable `systemd-resolved` on host nodes, and restore `/etc/resolv.conf` to the original. * A quick and dirty fix is to edit your Corefile, replacing `proxy . /etc/resolv.conf` with -the ip address of your upstream DNS, for example `proxy . 8.8.8.8`.
\ No newline at end of file +the ip address of your upstream DNS, for example `proxy . 8.8.8.8`. |