dig +bufsize
Cricket Liu
cricket at menandmice.com
Thu Mar 21 23:44:21 UTC 2002
Regardless of what I specify as an argument to dig's
+bufsize option, dig reports that it advertised a
buffer size of 4096:
$ dig @k.root-servers.net. +bufsize=1024
; <<>> DiG 9.2.0 <<>> @k.root-servers.net. +bufsize=1024
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27506
;; flags: qr aa rd; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 14
;; OPT PSEUDOSECTION:
; EDNS: version: 0, udp= 4096
;; QUESTION SECTION:
;. IN NS
$ dig @k.root-servers.net. +bufsize=2048
; <<>> DiG 9.2.0 <<>> @k.root-servers.net. +bufsize=2048
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52642
;; flags: qr aa rd; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 14
;; OPT PSEUDOSECTION:
; EDNS: version: 0, udp= 4096
;; QUESTION SECTION:
;. IN NS
So does +bufsize just set the corresponding option to 4096
regardless?
cricket
More information about the bind-workers
mailing list