Here's what the bind-users report said about www.monty.de: ``I recently
had to explain to customers that no it's not our fault that our name
servers can't resolve that name. And by the way, no it doesn't work on
the second try or the third.''
C'mon, everybody, try it! Ask your cache for the www.monty.de address.
I tried several BIND caches; they all failed. I've already explained in
detail how much work dnscache has to go through to find the address.
Elz seems to understand that the www.monty.de disaster is a powerful
argument against the relevant aspects of the DNS design. So now he's
denying the facts. He wants you to believe that www.monty.de is okay.
Robert Elz writes:
> ;; Total query time: 1850 msec
That's nice. Try again from an empty cache.
> Note that the answer had the AA bit set - it didn't just appear out
> of some local cache.
Don't be an idiot. That packet is straight from {ns,ns2}.norplex.net.
What you had in your cache was the addresses of those servers.
> so to find that A record, all that could have been needed (in practice)
> was just 2 round trips...
Don't be an idiot. In practice, most caches don't have the *.norplex.net
addresses lying around when they are asked about www.monty.de.
---Dan
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
