X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ian/git?a=blobdiff_plain;f=scripts%2Fnamed-conf.8;h=a75dd7fb440cf445763c94d915ef92946330579f;hb=f98e8767e057ec623069c0f12ba254ae17ab5ea3;hp=40e5955922a50f7856c5b7746af5242f616524c4;hpb=2474d69c46de4ae5f2f080ea94b5306d38c720fa;p=chiark-utils.git

diff --git a/scripts/named-conf.8 b/scripts/named-conf.8
index 40e5955..a75dd7f 100644
--- 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.
+
+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,