aboutsummaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorGravatar Miek Gieben <miek@miek.nl> 2016-04-03 20:07:15 +0100
committerGravatar Miek Gieben <miek@miek.nl> 2016-04-03 20:07:15 +0100
commit33d522385589f4c7ab486e71ab8eb7bf20bb13c8 (patch)
tree8400cf27cfb1d41ac04aa0d7385d7e32b82e436d /README.md
parent80007f4729ca31d4dcfc884fd3f36d9df7c7d5b7 (diff)
downloadcoredns-33d522385589f4c7ab486e71ab8eb7bf20bb13c8.tar.gz
coredns-33d522385589f4c7ab486e71ab8eb7bf20bb13c8.tar.zst
coredns-33d522385589f4c7ab486e71ab8eb7bf20bb13c8.zip
typos
Diffstat (limited to 'README.md')
-rw-r--r--README.md3
1 files changed, 2 insertions, 1 deletions
diff --git a/README.md b/README.md
index 92fc13402..d03b70e40 100644
--- a/README.md
+++ b/README.md
@@ -18,7 +18,8 @@ Currently CoreDNS is able to:
* Provide Logging.
There are corner cases not implement and some blatantly missing functionality; i.e. the secondary
-implement *does not* requery the primary -- *ever*.
+implementation *does not* requery the primary -- *ever*, leading to stale data if the server is
+not restarted.
But all in all, CoreDNS should already be able to provide you with enough functionality to replace
parts of BIND9, Knot, NSD or PowerDNS.