4 ms·
> without being able to perform these queries in tools like dig, a lot of sysadmin/support staff time would be wasted You don't want to be using ANY queries in
by geofft 12y ago
> without being able to perform these queries in tools like dig, a lot of sysadmin/support staff time would be wasted
You don't want to be using ANY queries in dig, anyway, because they already waste support-staff time. They're entirely too prone to tell you what's already in cache, which might not include the record type you wanted. (It'll probably work when talking to an authoritative server, but if you have to learn how to make things work against recursive/caching servers, it doesn't seem worth learning both methods.) If you want A records, ask for A records. If you want AAAA records or MX or TXT records, ask for AAAA or MX or TXT records. If someone else asks for A records, and then you ask for ANY records, you won't see the AAAA records, which can lead to a long wild-goose chase about who isn't supporting IPv6 properly. If someone else cached A, AAAA, and MX records, and you ask for ANY and don't see a TXT record, you can be super confused about why mail is failing a "nonexistent" SPF rule.
dig defaults to A, anyway. BIND's host command defaults to doing three queries, for A, AAAA, and MX.
- teddyh 12y agoYour point might have been correct if all you were querying was your recursive resolvers. But the ANY query is most useful with authoritative servers. So you’re wrong; ANY is very useful.
- geofft 12y agoIf you ever have reason to query both recursive and authoritative servers, then you need to know that you should avoid ANY for recursive servers, and you need to know how to query the specific record types you care about. So what's the advantage of having ANY around for authoritative ones?