Why must Comcast's DNS suck?

[njh603 at adelphia.net]

Comcast has recently bought out Adelphia and they are in the process of migrating customers over to Comcast.  I live in Londonderry and they did the
switchover on Monday.  Everyone around here was completely off the air ALL
day on Monday.  It just amazes me (being from the field of high availabilty services) that they couldn't come up with failover process that would provide minimal customer impact.  

---- Jerry Feldman <gaf at blu.org> wrote: 
> On Tue, 14 Nov 2006 11:19:49 -0500
> Paul Lussier <p.lussier at comcast.net> wrote:
> 
> > "Ben Scott" <dragonhawk at gmail.com> writes:
> > 
> > >   Really.  That's interesting.  I'm on Comcast (Dover, NH) and I
> > > haven't noticed any problems of that sort.  Any pattern to the sites,
> > > that you can discern?
> > 
> > Nope.  The two I can remember of hand are:
> > 
> >   www.evangelicaloutpost.com[1]
> >   www.shamusyoung.com[2]
> They come up fine for me:
> This is my resolv.conf. My router provides me with DNS from Comcast.
> nameserver 192.168.0.1
> nameserver 68.87.71.226
> nameserver 68.87.64.196
> 
> -- 
> Jerry Feldman <gaf at blu.org>
> Boston Linux and Unix user group
> http://www.blu.org PGP key id:C5061EA9
> PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9