Hi,
I'm not sure if it was already discussed on this list.
Why is BIND's dig getting a AD flag and kdig not?
Obviously sends dig the AD flag by default, but why have you decided this way?
dig +noall +comments @dotns1.aco.net univie.ac.at soa +qr
;; Sending:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52963
;; flags: rd ad; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: d2171ad4016ceb3d
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52963
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
kdig +noall +header @dotns1.aco.net univie.ac.at soa +qr
;; ->>HEADER<<- opcode: QUERY; status: NOERROR; id: 25583
;; Flags: rd; QUERY: 1; ANSWER: 0; AUTHORITY: 0; ADDITIONAL: 0
;; ->>HEADER<<- opcode: QUERY; status: NOERROR; id: 25583
;; Flags: qr rd ra; QUERY: 1; ANSWER: 1; AUTHORITY: 0; ADDITIONAL: 0
cheers,
-arsen