[113175] in North American Network Operators' Group
Re: ISC DLV
daemon@ATHENA.MIT.EDU (David Conrad)
Sun Apr 5 12:21:41 2009
From: David Conrad <drc@virtualized.org>
To: bmanning@vacation.karoshi.com
In-Reply-To: <20090405100931.GA31202@vacation.karoshi.com.>
Date: Sun, 5 Apr 2009 06:19:35 -1000
Cc: Mark Andrews <Mark_Andrews@isc.org>, nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Apr 5, 2009, at 12:09 AM, bmanning@vacation.karoshi.com wrote:
> On Sun, Apr 05, 2009 at 07:37:15PM +1000, Mark Andrews wrote:
>>
>> The fault has been rectified. We are still looking into the
>> underlying cause and what procedural changes need to be made to
>> prevent a repeat occurance.
>>
>> Mark Andrews, ISC
>
> could ISC be a bit more open and transparent on what the
> underlying cause was, the path/steps between cause and effect,
> and the range of options/choices for mitigation and why the
> one chosen (presuming it was a procedural issue) was/is the
> best choice.
You should definitely demand your money back. Given the root servers
don't provide this level of accountability, not sure why you think ISC
should.
Stuff happens. If you've chosen to share fate with ISC for name
resolution via DLV, then you should accept that it does and anticipate
these sorts of outages. I'm sure the folks at ISC will attempt to
minimize reoccurrence.
Regards,
-drc
