doc: improve text for listening on wildcard addresses

The different addresses don't need to share an interface.
Also provide more details on what fails.

diff --git a/doc/config-network-server.rst b/doc/config-network-server.rst
index e4d6c63c41e19bbbedd76b1b23678bf0a2c013bd..807c44a4754aceea8ece522e1915f643be0388f1 100644 (file)
--- a/doc/config-network-server.rst
+++ b/doc/config-network-server.rst
@@ -69,7 +69,8 @@ First you need to decide what service should be available on given IP address
 
 .. warning::
 
-    On machines with multiple IP addresses avoid listening on wildcards ``0.0.0.0`` or ``::``. Knot Resolver could answer from different IP addresses if the network address ranges overlap, and clients would probably refuse such a response.
+   On machines with multiple IP addresses avoid listening on wildcards ``0.0.0.0`` or ``::``.
+   If a client can be reached through multiple addresses, UDP answers from a wildcard address might pick a wrong source address, and such responses should then get refused.
 
 
 .. _config-network-proxyv2:

diff --git a/doc/gettingstarted-config.rst b/doc/gettingstarted-config.rst
index b1f7d377eddaeaacd3bc597457fe6e04f98973ca..50d25a0ab0b1ce599fedd82211acfe81954094b2 100644 (file)
--- a/doc/gettingstarted-config.rst
+++ b/doc/gettingstarted-config.rst
@@ -60,8 +60,8 @@ For more details look at the :ref:`network configuration <config-network>`.
 
 .. warning::
 
-   On machines with multiple IP addresses on the same interface avoid listening on wildcards ``0.0.0.0`` or ``::``.
-   Knot Resolver could answer from different IP addresses if the network address ranges overlap, and clients would refuse such a response.
+   On machines with multiple IP addresses avoid listening on wildcards ``0.0.0.0`` or ``::``.
+   If a client can be reached through multiple addresses, UDP answers from a wildcard address might pick a wrong source address, and such responses should then get refused.
 
 
 .. _examle-internal: