diff options
| author |  StormXX <stormxx@1024.engineer>
| 2018-12-07 17:45:13 +0800 |
|---|---|---|
| committer |  Miek Gieben <miek@miek.nl>
| 2018-12-07 09:45:13 +0000 |
| commit | 16197a1addb69dafffd5f8ffca1d00273831b583 (patch) | |
| tree | 402fb6077896c55beaca021dc0f1691358964028 /plugin | |
| parent | 4a3f5cc41eabacb9552c6d8cba82b23801c0edf4 (diff) | |
| download | coredns-16197a1addb69dafffd5f8ffca1d00273831b583.tar.gz coredns-16197a1addb69dafffd5f8ffca1d00273831b583.tar.zst coredns-16197a1addb69dafffd5f8ffca1d00273831b583.zip | |
fix a document error (#2376)
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 9272160ff..5062dfa3d 100644 --- a/plugin/loop/README.md +++ b/plugin/loop/README.md @@ -70,7 +70,7 @@ This is because Kubernetes will try to restart the Pod every time CoreDNS detect A common cause of forwarding loops in Kubernetes clusters is an interaction with a local DNS cache 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 +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` as a list of upstreams to proxy/forward requests to. Since it contains a loopback address, CoreDNS ends up forwarding requests to itself. |