Skip to content

C
Coredns
Commit 16197a1a authored by StormXX's avatar StormXX Committed by Miek Gieben
Browse files
Options

fix a document error (#2376)

parent 4a3f5cc4
Hide whitespace changes
Inline Side-by-side
Showing with 1 addition and 1 deletion
plugin/loop/README.md
View file @ 16197a1a
...@@ -70,7 +70,7 @@ This is because Kubernetes will try to restart the Pod every time CoreDNS detect ...@@ -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 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 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 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` 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 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.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment