ICANN/GNSO GNSO Email List Archives

[ga]


<<< Chronological Index >>>    <<< Thread Index >>>

Re: [ga] ISC opens Internet crisis center. <-- Did they just forget the BIND fiasco over Site Finder?

  • To: Jeff Williams <jwkckid1@xxxxxxxxxxxxx>
  • Subject: Re: [ga] ISC opens Internet crisis center. <-- Did they just forget the BIND fiasco over Site Finder?
  • From: Stephane Bortzmeyer <bortzmeyer@xxxxxx>
  • Date: Thu, 23 Oct 2003 10:05:57 +0200
  • Cc: General Assembly of the DNSO <ga@xxxxxxxxxxxxxx>
  • In-reply-to: <3F97306A.B18A4D0D@ix.netcom.com>
  • Organization: NIC France
  • References: <3F97306A.B18A4D0D@ix.netcom.com>
  • Sender: owner-ga@xxxxxxxxxxxxxx
  • User-agent: Mutt/1.5.4i

On Wed, Oct 22, 2003 at 06:35:38PM -0700,
 Jeff Williams <jwkckid1@xxxxxxxxxxxxx> wrote 
 a message of 25 lines which said:

>   I have to wonder, as I am very sure Verisign and and a number of
> other Site Finder converts, as to whether stakeholders/users have
> forgotten so soon the BIND adjustment/patches fiasco over trying to
> address Site Finder?

[Not speaking for ISC, of course, but <disclaimer>AFNIC is a member of
the BIND forum</disclaimer>.]

This is absolutely ridiculous. There was no fiasco. ISC, maintainer of
BIND (by far the most widely used software for caching/forwarding name
servers), addressed very quickly a vocal demand from many of its
users. ISC released a new version of BIND, there was a bug, then a new
version, there was also a bug and finally the proper one. 

Do note that the new features in BIND to fix the Verisign problem were
all OFF by default, so it was the responsability of the name server
administrator to turn them on or not.

There was some technical problems with "funny" cases because the DNS
is a complicated beast, badly specified (dozens of RFC are
authoritative when you write or maintain a DNS software), and there
was a huge pressure from the community so everything was done in a
hurry (remember that Verisign made no prior warning). Other nameserver
software, like PowerDNS, which released similar patches, experienced
the same problems.

These bugs created a few temporary problems, much less than Verisign's
bold attempt to typosquatt everything in .com/.net.

Sorry for the long message to correct an obvious troll.




<<< Chronological Index >>>    <<< Thread Index >>>