On Wed, 2004-09-08 at 13:05, David Malone wrote:
As the next RIPE meeting is rolling up, I just thought I'd raise the AAAA lookup misbehaviour thread again. To briefly remind you of where we'd got to:
1) I'd written up a short describing the problem with authoritative servers and recommending that new name servers should be tested before deployment. 2) Alvaro and Colm had highlighted some problems with client resolver libraries, but it wasn't clear if a description of these problems should live in the same document. 3) We were trying to figure out what action could be taken to encourage people to fix existing problem name servers.
So, other than the hall of shame, what options do we have to encourage people to fix their software? Working with vendors of DNS solutions is certainly a good idea, and the dns-wg's name could be useful when convincing vendors to take action.
Another possibility would be to recommend that when problem DNS servers are found, then they should be considered lame and so dropped from the advertised list of NSs for a zone.
Any other ideas?
Notez bien that some software is also doing A6 lookups, even bind9 does this upto 9.3.x afaik. Add a small item about ip6.int and ip6.arpa and maybe even discussing (again as the previous time nicely got killed) about the quick removal of ip6.int in total. Greets, Jeroen