Unless I misunderstand what you mean, my version of BIND (8.2.2p3) doesn't do that.
$ host -a 2.254.92.204.in-addr.arpa 2.254.92.204.in-addr.arpa PTR most.weird.com 2.254.92.204.in-addr.arpa PTR mail.weird.com
Interesting. I actually haven't tried this since BIND 4. It made sense that it wouldn't so I assumed it shouldn't and further assumed that in BIND 8 that it didn't as well. (Sorry about that last sentence!) Anyways, I think you catch up with me in your next paragraph here ... So does the reverse resolve work correctly with the two PTR responses for most resolvers? Karyn
I don't think it round-robins them though (that's the order they appear in my zone file and several queries in a row always return them in that order -- I've not read the code recently so I don't remember for sure), because normally you don't want to round-robin them, and if you did you wouldn't be able to distinguish between the primary host and its aliases with the BIND resolver library:
$ host -a 204.92.254.2 Name: most.weird.com Address: 204.92.254.2 Aliases: mail.weird.com
(The "primary", or "official" hostname comes from the "h_name" field of "struct hostent", which is returned by gethostbyaddr() and friends.)
<< Yes, I know what kind of flack that this will lead to, but the logic isn't that wierd...
I can't give you any flack about multiple PTRs, I use them too! :-)
-- Greg A. Woods
+1 416 218-0098 VE3TCP <gwoods@acm.org> <robohack!woods> Planix, Inc. <woods@planix.com>; Secrets of the Weird <woods@weird.com>