chiark
/
gitweb
/
~ian
/
chiark-utils.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
Reference DJB
[chiark-utils.git]
/
scripts
/
named-conf.8
diff --git
a/scripts/named-conf.8
b/scripts/named-conf.8
index 40e5955922a50f7856c5b7746af5242f616524c4..a75dd7fb440cf445763c94d915ef92946330579f 100644
(file)
--- a/
scripts/named-conf.8
+++ b/
scripts/named-conf.8
@@
-362,6
+362,12
@@
publishing glue for them, there is no chance of anything longer than a
probably best to maintain this as the status quo, despite the
performance problem this implies for BIND 8 caches. This is what the
serverless\-glueless directive is for.
probably best to maintain this as the status quo, despite the
performance problem this implies for BIND 8 caches. This is what the
serverless\-glueless directive is for.
+
+Dan Bernstein has some information and examples about this at
+.UR http://cr.yp.to/djbdns/notes.html#gluelessness
+http://cr.yp.to/djbdns/notes.html#gluelessness
+.UE
+but be warned that it is rather opinionated.
.SH SECURITY
chiark\-named\-conf is supposed to be resistant to malicious data in
the DNS. It is not resistant to malicious data in its own options,
.SH SECURITY
chiark\-named\-conf is supposed to be resistant to malicious data in
the DNS. It is not resistant to malicious data in its own options,