Why must Comcast's DNS suck?

[Ben Scott]

On 11/14/06, Paul Lussier <p.lussier at comcast.net> wrote:
> Over the past couple of weeks I've noticed that sites I can get to
> both easily and quickly from work are completely unreachable from
> home.  From Comcast's perspective, these sites seem to not even exist.

  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?

  Also, are you using manually configured DNS servers, or what they
give out via DHCP?  If the former, you might want to try the later.  I
know they've been changing things around as of late.

> Is this intentional censoring on Comcast's part, or just incompetance
> at maintaining a DNS server infrastructure?

  "Never attribute to malice that which can be adequately explained by
stupidity."

> How about the GNHLUG server?  Can we make that a DNS server as a
> "membership" benefit?

  Well, from a policy standpoint, I have no objections, but I wonder
about some technical aspects.  I'm not sure about the performance of
that system.  More importantly, unless you have a static IP address,
how do we open it up to just "members"?

-- Ben