diff options
author | 2021-01-15 11:26:34 -0500 | |
---|---|---|
committer | 2021-01-15 17:26:34 +0100 | |
commit | 5c07ab7b78f088557a6abec3cad6a262243d6131 (patch) | |
tree | 480e32b4a1b22e4c011509746c1642493e52528e | |
parent | b2a22eff04fbfd9801d865f8a7702d6f62dfac14 (diff) | |
download | coredns-5c07ab7b78f088557a6abec3cad6a262243d6131.tar.gz coredns-5c07ab7b78f088557a6abec3cad6a262243d6131.tar.zst coredns-5c07ab7b78f088557a6abec3cad6a262243d6131.zip |
doc bind collision issue (#4394)
Signed-off-by: Chris O'Haver <cohaver@infoblox.com>
-rw-r--r-- | plugin/bind/README.md | 20 |
1 files changed, 20 insertions, 0 deletions
diff --git a/plugin/bind/README.md b/plugin/bind/README.md index fec5511ab..761aa056a 100644 --- a/plugin/bind/README.md +++ b/plugin/bind/README.md @@ -49,3 +49,23 @@ The following sample is equivalent to the preceding: bind ::1 } ~~~ + +## Bugs + +When defining more than one server block, take care not to bind more than one server to the same +address and port. Doing so will result in unpredictable behavior (requests may be randomly +served by either server). Keep in mind that *without* the *bind* plugin, a server will bind to all +interfaces, and this will collide with another server if it's using *bind* to listen to an interface +on the same port. For example, the following creates two servers that both listen on 127.0.0.1:53, +which would result in unpredictable behavior for queries in `a.bad.example.com`: + +``` +a.bad.example.com { + bind 127.0.0.1 + forward . 1.2.3.4 +} + +bad.example.com { + forward . 5.6.7.8 +} +```
\ No newline at end of file |