twisted.names.client.Resolver should not use ANY dns query type to resolve names.
|Reported by:||Marek Kowalski||Owned by:||Marek Kowalski|
Description (last modified by )
I run into this problem when trying to resolve some name. It was giving me different result depending on the dns server with the ANY query type. (the result of both calls can be found in the attachment).
I asked on #dns channel which query type should be used, and this is the explanation I got:
19:24 <hawk> kowal: ANY is a strange beast to begin with, I'm not sure what to expect actually 19:28 <hawk> kowal: ANY is not really reliable for any real usage when querying a caching server 19:30 <hawk> kowal: The general problem with ANY is that a caching server is allowed to just return whatever it has in the cache. Ie, if you send a query for ANY and there are for instance both A and AAAA records for that name, it's allowed to just give you whatever it already has... so maybe just the A, or just the AAAA or both... you don't really know what you'll get.
Therefore I suggest we use lookupAddress instead of lookupAllNames in the implementation of getHostByName (diff attached).