Mirrors/coredns
1
0
Fork 0
mirror of https://github.com/coredns/coredns.git synced 2025-10-28 00:34:24 -04:00
Code Issues Packages Projects Releases Wiki Activity

better README

Browse Source 
Signed-off-by: Miek Gieben <miek@miek.nl>
This commit is contained in:
Miek Gieben
2020-07-14 21:21:06 +02:00
parent 45ff6dd1c4
commit c5a36c70c3
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
plugin/traffic/README.md
View File

@@ -165,14 +165,14 @@ endpoint-2.web.lb.example.org. 5 IN A 127.0.2.1
## Bugs ## Bugs
Credentials are not implemented. Bootstrapping is not fully implemented, *traffic* will connect to Credentials are not implemented. Bootstrapping is not fully implemented, *traffic* will connect to
the first working **TO** address, but then stops short of re-connecting to he endpoints is received the first working **TO** address, but then stops short of re-connecting to the endpoints of the
for the management **CLUSTER**. management **CLUSTER**.
Load reporting is not supported for the following reason: A DNS query is done by a resolver. Load reporting is not supported for the following reason: A DNS query is done by a resolver.
Behind this resolver (which can also cache) there may be many clients that will use this reply. The Behind this resolver (which can also cache) there may be many clients that will use this reply. The
responding server (CoreDNS) has no idea how many clients use this resolver. So reporting a load of responding server (CoreDNS) has no idea how many clients use this resolver. So reporting a load of
+1 on the CoreDNS side can results in anything from 1 to 1000+ of queries on the endpoint, making +1 on the CoreDNS side can results in anything from 1 to 1000+ of queries on the endpoint, making
the load reporting from *traffic* highly inaccurate. the load reporting from the *traffic* plugin highly inaccurate. Hence it is not done.
## Also See ## Also See