Re: [dns-wg] AAAA lookup misbehaviour
- Date: Thu, 9 Sep 2004 11:12:41 +0200
On 8 Sep, 2004, 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?
Writing a RIPE document. People use them as reference material when
they are well written, both within and outside the RIPE region
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.
Sure, buy me a beer. I am easy to convince :-)
Now seriously, we try to do the right thing, we may have bugs some
times. For instance there was some time ago a bug that went like this:
1679. [bug] When there was a single nameserver with multiple
addresses for a zone not all addresses were
tried.
[RT #11706]
e.g.
If the server had one AAAA and one A, then A would not be
tried.
They will mark all addresses bad if they get a bad response
from one of the addresses (bad response != no response).
Although you could argue this goes in your favour as IPv6 promoter.
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.
Well, that would depend on the nature of the misbehaviour. I am looking
forward to your DNS-wg contribution.
Joao
|
you are here: RIPE -> RIPE Maillists > Archives
