aboutsummaryrefslogtreecommitdiff
path: root/plugin
diff options
context:
space:
mode:
authorGravatar Chris O'Haver <cohaver@infoblox.com> 2018-12-05 16:20:20 -0500
committerGravatar corbot[bot] <corbot[bot]@users.noreply.github.com> 2018-12-05 21:20:20 +0000
commit9a393ac5c8e57b7fa38c73eb2dc6a96cf51ad800 (patch)
treedbdb7aa82b727c5007b0d23d032b5a196490f5a7 /plugin
parent59a49c5ff7eeb6dad2e38ce8ccd5c4682e087005 (diff)
downloadcoredns-9a393ac5c8e57b7fa38c73eb2dc6a96cf51ad800.tar.gz
coredns-9a393ac5c8e57b7fa38c73eb2dc6a96cf51ad800.tar.zst
coredns-9a393ac5c8e57b7fa38c73eb2dc6a96cf51ad800.zip
clean pre-submit checks (#2367)
Automatically submitted.
Diffstat (limited to 'plugin')
-rw-r--r--plugin/loop/README.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/plugin/loop/README.md b/plugin/loop/README.md
index e10e1f4b7..9272160ff 100644
--- a/plugin/loop/README.md
+++ b/plugin/loop/README.md
@@ -71,13 +71,13 @@ A common cause of forwarding loops in Kubernetes clusters is an interaction with
on the host node (e.g. `systemd-resolved`). For example, in certain configurations `systemd-resolved` will
put the loopback address `127.0.0.53` as a nameserver into `/etc/resolv.conf`. Kubernetes (via `kubelet`) by default
will pass this `/etc/resolv/conf` file to all Pods using the `default` dnsPolicy rendering them
-unable to make DNS lookups (this includes CoreDNS Pods). CoreDNS uses this `/etc/resolv.conf`
+unable to make DNS lookups (this includes CoreDNS Pods). CoreDNS uses this `/etc/resolv.conf`
as a list of upstreams to proxy/forward requests to. Since it contains a loopback address, CoreDNS ends up forwarding
-requests to itself.
+requests to itself.
There are many ways to work around this issue, some are listed here:
-* Add the following to `kubelet`: `--resolv-conf <path-to-your-real-resolv-conf-file>`. Your "real"
+* Add the following to `kubelet`: `--resolv-conf <path-to-your-real-resolv-conf-file>`. Your "real"
`resolv.conf` is the one that contains the actual IPs of your upstream servers, and no local/loopback address.
This flag tells `kubelet` to pass an alternate `resolv.conf` to Pods. For systems using `systemd-resolved`,
`/run/systemd/resolve/resolv.conf` is typically the location of the "real" `resolv.conf`,