which appear to come from your real nameservers. It relies on the
full-service resolvers listed in resolv.conf to handle these tasks.
-For secure and reasonable operation you MUST run a full-service
+For secure and reasonable operation you should run a full-service
nameserver on the same system as your adns applications, or on the
-same local, fully trusted network. You MUST only list such
+same local, fully trusted network. You should only list such
nameservers in the adns configuration (eg resolv.conf).
-You MUST use a firewall or other means to block packets which appear
+You should use a firewall or other means to block packets which appear
to come from these nameservers, but which were actually sent by other,
untrusted, entities.
understand even how to ask a DNSSEC-aware nameserver to perform the
DNSSEC cryptographic signature checking.
+adns does use random query ids, since 1.7.0. (In the unlikely event
+this is not possible, adns will log a message to stderr.)
+The position is similar to other stub resolvers, such as the one in
+glibc used by gethostbyname etc.
+
COPYRIGHT
adns (1.6.3~) UPSTREAM; urgency=medium
- *
+ * Select query IDs randomly using getentropy, if we can.
+ See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1145407.
--