My ISP's nameserver confuses the resolver in glibc 2.3.2 and BIND 9.2.1

[Jonathan de Boyne Pollard]

dh> Why is the resolver so picky? 

Because although the actual _text_ of RFC 1034 doesn't explicitly mandate an
ordering of the resource record sets in a chain of client-side aliases in a
response, for simplicity of implementation most DNS client softwares are
written with the assumption that there _is_ such an ordering, and that that
ordering will be the same ordering as would be produced by the example server
algorithm in RFC 1034 (although the example algorithm is actually itself
ambiguous in this regard, too).  Without this assumption, the processing of
chains of client-side aliases in responses changes from O(N) to O(N*N), and
also has to employ loop detection.

dh> The nameserver in question is on 203.220.32.107

... and it's seriously broken.  Complain to your ISP about its faulty service.