nsd 4.1.6 gives us minimal-responses config option and I think we
should enable it in nsd.conf.
>From the man page:
minimal-responses: <yes or no>
Enable minimal responses for smaller answers. This makes
packets smaller. Extra data is only added for referrals, when
it is really necessary. This is different from the --enable-
minimal-responses configure time option, that reduces packets,
but exactly to the fragmentation length, the nsd.conf option
reduces packets as small as possible. The default is no.
I consider smaller packets a good thing in the context of DNS :)
e.g.:
minimal-responses: yes
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40454
;; flags: qr aa; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;tlakh.xyz. IN A
;; ANSWER SECTION:
tlakh.xyz. 86400 IN A 139.162.223.167
;; Query time: 34 msec
;; SERVER: 139.162.223.167#53(139.162.223.167)
;; WHEN: Sat Apr 15 11:25:13 2017
;; MSG SIZE rcvd: 43
what we currently have:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41501
;; flags: qr aa; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0
;; QUESTION SECTION:
;tlakh.xyz. IN A
;; ANSWER SECTION:
tlakh.xyz. 86400 IN A 139.162.223.167
;; AUTHORITY SECTION:
tlakh.xyz. 86400 IN NS a.sec.ns.sha256.net.
tlakh.xyz. 86400 IN NS ns6.gandi.net.
;; Query time: 31 msec
;; SERVER: 139.162.223.167#53(139.162.223.167)
;; WHEN: Sat Apr 15 11:26:23 2017
;; MSG SIZE rcvd: 100
It is left as an excercise to the reader to observe what happens with
dnssec.
Comments / OKs?
diff --git etc/nsd.conf etc/nsd.conf
index c5491605a24..6e8122e041b 100644
--- etc/nsd.conf
+++ etc/nsd.conf
@@ -4,6 +4,7 @@ server:
hide-version: yes
verbosity: 1
database: "" # disable database
+ minimal-responses: yes
## bind to a specific address/port
# ip-address: 192.0.2.53
--
I'm not entirely sure you are real.
