[lug] DNS Problems: Is it me, or is it Comcast?

[Michael Deck]

At 12:48 PM 10/4/2004, David Anselmi wrote:

>Michael Deck wrote:
> > At 11:40 AM 10/4/2004, David Anselmi wrote:
> >
> >> Michael Deck wrote:
> >> [...]
> >>
> >> Apparently your home office DNS cache is broken.  Your name server
> >> (198.49.126.122) is working fine (as indicated by others' replies).
> >
> >
> > David, I'm not sure where the cache is located. Just to explain, my
> > "home office" is a Linux box behind a router behind a cable box. I don't
> > *think* that Linux box is caching DNS but if it is, how would I clear it?
>
>Your DNS cache is the servers that answer requests from clients (e.g.,
>your Linux box).  They are listed in /etc/resolv.conf.

Ok, those are comcast's.


>Probably the name servers in your resolv.conf are Comcast's (set there
>by DHCP from your router, which gets them by DHCP from Comcast).  Can
>you ping them?  Do they match what Comcast's support page says they
>should be?

I got several answers from comcast but the final answer is, they're the 
right servers.


>You can query them specifically with host or dig.  If they don't answer
>correctly (assuming time for their caches to refresh after any changes
>you've made) you probably have to talk to their admins to find out why.

After spending more than an hour with various avenues of support at 
Comcast, I can definitely say they have no clue but they all agree the 
problem is that my host is sending "bad information". They can't tell me 
what's bad about it, or what I can do, and they have provided other answers 
that are all very wrong, so I'm stumped. I cleaned up almost all the 
warnings listed at dnsreport.com, and we'll see if maybe they're just more 
sensitive than anyone else.

Unfortunately you can't actually talk to someone at comast who knows anything.




Michael Deck
Cleanroom Software Engineering, Inc.