TrueCloudLab/coredns
16
0
Fork 2
Code Issues Pull requests 4 Projects Releases Packages Wiki Activity Actions

Update README.md (#2213)

Browse source
This commit is contained in:
Chris O'Haver 2018-10-18 10:19:22 -04:00 • committed by Miek Gieben
parent 4215ef0279
commit db92d5ecc3
1 changed files with 3 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
plugin/loop/README.md
View file

@ -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`.
the ip address of your upstream DNS, for example `proxy . 8.8.8.8`.