Commit Diff
Diff:
f5e44f38c7f9981d7a0eac6ab91a0c46d2c2bcbc
b93bcc6282b53b2bdb3ff663a4f6dd2a4075ad86
Commit:
b93bcc6282b53b2bdb3ff663a4f6dd2a4075ad86
Tree:
b59c257ae024545c9bcb1ebb315489f898dfaf28
Author:
pbug <pbug@delphinusdns.org>
Committer:
pbug <pbug@delphinusdns.org>
Date:
Tue Nov 3 20:18:28 2009 UTC
Message:
* have a "what it can't do" section
blob - a4987b8526c7807c47bb6397ec6c44724a0deaa2
blob + 9b82307deba59bba840e10238b560d336e82e165
--- README
+++ README
@@ -1,10 +1,11 @@
-$Id: README,v 1.7 2008/07/10 18:03:06 pbug Exp $
+$Id: README,v 1.8 2009/11/03 20:18:28 pbug Exp $
1. README
2. WHY WILDCARDNS?
3. INSTALL HINTS
4. COMPATIBILITY
5. EXAMPLES
+6. WHAT IT CAN'T DO
1. README
---------
@@ -122,3 +123,17 @@ DragonFlyBSD 1.10 | yes | yes
-----------
in the directory "examples" are a few examples from working configs.
+
+
+6. WHAT IT CAN'T DO
+-------------------
+
+6.1 DELEGATIONS
+---------------
+
+It cannot delegate zones to another nameserver. The wildcarding feature
+would defeat this anyhow since it searches every label from the query to
+see if there is a zone above it before it gives an answer. The reply
+to delegations looks different as outlined in RFC 1034 section 6.2.6, this
+sort of reply wildcarddnsd can't do. It's best to use BIND for this.
+
repomaster@centroid.eu