They should fix their broken resolvers then, that’s not for me to work around. I don’t think it’s actually a big problem in practice though, because

1. my primary nameserver is actually fairly reliable, and
2. it looks like the nameservers in the NS query are in a randomized order (until the response is cached, of course)