Why must Comcast's DNS suck?

[Paul Lussier]

"Ben Scott" <dragonhawk at gmail.com> writes:

>   Those reverse to:
>
> 24.34.240.9	chlm2-pdns-tmp.chelmsfdrdc2.ma.boston.comcast.net.
> 24.34.241.9	chlm2-2dns-tmp.chelmsfdrdc2.ma.boston.comcast.net.
> 68.87.64.196	ns.inflow.pa.bo.comcast.net.
>
>   Note the "-tmp" in those first two names.  Meanwhile, I have
>   these, from DHCP:
>
> 68.87.71.226	cns.chelmsfdrdc2.ma.boston.comcast.net.
> 68.87.73.242	cns.manassaspr.va.dc02.comcast.net.

Interesting.  I don't recall ever mucking with my dhcp config such
that /etc/resolv.conf wouldn't get updated.  I suppose it's possible...

>   At a guess, it looks like you have stale entries in your resolv.conf file.

Definitely.  Changing them to what you have makes those sites resolve
instantly.  Now to hunt down why those were static...

>   Of course, as others suggested, setting up your own local,
> full-service, recursive resolver is probably a good idea, too.

I might do that if I feel the need to build yadnss :)

-- 
Seeya,
Paul "who sometimes just wants to be a user"
--
Key fingerprint = 1660 FECC 5D21 D286 F853  E808 BB07 9239 53F1 28EE

A: Yes.                                                               
> Q: Are you sure?                                                    
>> A: Because it reverses the logical flow of conversation.           
>>> Q: Why is top posting annoying in email?