On Mon, 9 Apr 2007, Ivo Smits wrote: > Holy.. whatever... > > When issuing a query for an A record, it indeed ONLY returns the SOA record, > which is invalid (it should return the NS record..) > When issuing a query for a MX recors, it returns some MX records AND the NS > records (no SOA, but we didnt ask for that one): > returns.bulk.yahoo.com. 1800 IN MX 1 c5.bullet.mud.yahoo.com. > returns.bulk.yahoo.com. 1800 IN MX 1 c6.bullet.mud.yahoo.com. > returns.bulk.yahoo.com. 1800 IN MX 1 c1.bullet.mud.yahoo.com. > returns.bulk.yahoo.com. 1800 IN MX 1 c2.bullet.mud.yahoo.com. > returns.bulk.yahoo.com. 1800 IN MX 1 c3.bullet.mud.yahoo.com. > returns.bulk.yahoo.com. 1800 IN MX 1 c4.bullet.mud.yahoo.com. > yahoo.com. 172800 IN NS ns2.yahoo.com. > yahoo.com. 172800 IN NS ns1.yahoo.com. > yahoo.com. 172800 IN NS ns3.yahoo.com. > yahoo.com. 172800 IN NS ns4.yahoo.com. > yahoo.com. 172800 IN NS ns5.yahoo.com. > yahoo.com. 172800 IN NS ns8.yahoo.com. > yahoo.com. 172800 IN NS ns9.yahoo.com. > ;; Received 499 bytes from 66.218.71.63#53(ns1.yahoo.com) in 173 ms > > Your resolver should (recursively) try nameservers until it has its answer, > so if it gets the answer to the MX query from the yahoo.com nameserver, it > should use that one and forget about any lower levels, like dig does. This > also helps when using a (decent) recursor. You could even use the same > routine for the smartdnshost! :p
XMail tried to find the closest authoritative NS of the host it wanted the MX, and then issue the query. That host gives out CNAME pointing to other CNAMES (?!?) when doing that (see above), and that prolly the reason why DNSReport pukes on it. I now changed the code to issue the query directly from top, and it seems to work. - Davide - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
