On Thu, 25 Apr 2002 11:30:27 +0900, Jun-ichiro itojun Hagino <itojun@itojun.org> said:
there are name server implementations (probably load balancing product) that responds with NXDOMAIN, when it should respond with NOERROR with empty reply. one example is news.bbc.co.uk. this symptom not only confuse IPv6-ready client resolvers, but also has bad effect against negative caching and email delivery (if MX is responded with NODOMAIN).
do you know: - name of particular implementation which have/had this bug? - other examples of nameservers that behave like this? (windowsupdate.microsoft.com behaved like this in Feb 2002, but they are already fixed) - how can we get people to fix it? (client side workaround should not be populated, just to be sure)
There are apparently several products that have this problem, some of which are sufficiently widely enough deployed that since Sendmail 8.11.3 or so, there has been a configure option 'WorkAroundBrokenAAAA' (available as a FFR in 8.11.3, and in the base code as of 8.12.0. I am told by people who have tripped over this problem more often than I have that *early* releases of djbdns did this - but that it is fixed in anything resembling a current release so the "right" fix is getting the offender to upgrade his software (which is often futile...) -- Valdis Kletnieks Computer Systems Senior Engineer Virginia Tech