[dns-operations] named actually asks for ANY

[Robert Martin-Legene]

Hi all.

Here I (and possibly one or two others) had the belief that named
would "never ask for ANY". I was blackboxtesting BIND with tcpdump and
asked it with

$ dig @127.0.0.1 aq. any

and here's the (for me) remarkable result (I have removed time stamps):

192.168.11.129.53 > 198.41.0.4.53:  39426 [1au] ANY? aq. (31)
192.168.11.129.53 > 198.41.0.4.53:  19713 [1au] NS? . (28)
198.41.0.4.53 > 192.168.11.129.53:  39426- 4/4/6 NS FLAG.EP.NET., NS
SLAVE1.STH.NETNOD.SE., NS NS-EXT.ISC.ORG., NS NS1.DNS.aq. (288)
198.41.0.4.53 > 192.168.11.129.53:  19713*- 13/0/14 NS
E.ROOT-SERVERS.NET., NS D.ROOT-SERVERS.NET., NS A.ROOT-SERVERS.NET.,
NS H.ROOT-SERVERS.NET., NS C.ROOT-SERVERS.NET., NS
G.ROOT-SERVERS.NET., NS F.ROOT-SERVERS.NET., NS B.ROOT-SERVERS.NET.,
NS J.ROOT-SERVERS.NET., NS K.ROOT-SERVERS.NET., NS
L.ROOT-SERVERS.NET., NS M.ROOT-SERVERS.NET., NS I.ROOT-SERVERS.NET.
(447)

Is this supposed to happen? I thought it'd only give you what it had
in it's cache prior to the req, if you asked it for ANY.

-- Robert, .dk