Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Sign in / Register
Toggle navigation
C
Coredns
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Locked Files
Issues
0
Issues
0
List
Boards
Labels
Service Desk
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Security & Compliance
Security & Compliance
Dependency List
License Compliance
Packages
Packages
List
Container Registry
Analytics
Analytics
CI / CD
Code Review
Insights
Issues
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Railgun
Coredns
Commits
db92d5ec
Commit
db92d5ec
authored
Oct 18, 2018
by
Chris O'Haver
Committed by
Miek Gieben
Oct 18, 2018
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update README.md (#2213)
parent
4215ef02
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
3 additions
and
1 deletion
+3
-1
plugin/loop/README.md
plugin/loop/README.md
+3
-1
No files found.
plugin/loop/README.md
View file @
db92d5ec
...
@@ -54,6 +54,7 @@ DNS servers. This is a fatal error because operating with an infinite loop will
...
@@ -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.
memory and CPU until eventual out of memory death by the host.
A forwarding loop is usually caused by:
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`
*
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.
*
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
...
@@ -75,9 +76,10 @@ to proxy/forward requests to. Since it contains a local address, CoreDNS ends u
requests to itself.
requests to itself.
There are many ways to work around this issue, some are listed here:
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
*
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`
,
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`
.
`/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.
*
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
*
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`
.
\ No newline at end of file
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment