The problem is that Comcast is still handing out attbi.com name
servers via DHCP. They should be handing out 66.45.25.71 and
66.45.25.72 as those are comcast name servers. The attbi.com name
servers are broken. Sometimes they resolve, sometimes they don't.
Tommithy
daytripper <(E-Mail Removed)> wrote in message news:<(E-Mail Removed)>. ..
> On Fri, 19 Sep 2003 22:28:43 -0600, JD <(E-Mail Removed)>
> wrote:
>
> >This seems odd and I couldn't find anything via Google, so here
> >goes...
> >
> >I'm in the Denver area, using Comcast (was AT&T Broadband until this
> >past spring) with an RCA cable modem. I've got the Linksys BEFW11S4
> >(the 4-port switch) and it doesn't have a version number on the label
> >like some of the newer ones did . The firmware is version 1.44.2z,
> >which is the most recent.
> >
> >Over the last month or so, DNS seems to just "fall asleep" for some
> >reason. All of the machines on the network (XP Pro) are unable to get
> >to the outside world, though they can see the router and each other
> >fine. This seems to happen a couple/few times a week. This week, it
> >seems like I'm able to "wake it up" by doing the following:
> >
> >1. Log into the router's admin interface and make note of its WAN
> >side IP address (from Comcast).
> >
> >2. Ping that address (works fine) and the router responds.
> >
> >3. Make a note of the "Default Gateway" (Comcast's gateway) on the
> >router's "Status" page. Ping that IP address and I DO get a response.
> >
> >4. I then make a note of the two valid IP addresses listed in the DNS
> >section of the router's "Status" page. I say "two valid" because
> >there's a third that's just zeros.
> >
> >5. I can then ping both of those successfully! From this point, it
> >seems the LAN/client machines are then able to browse just fine,
> >check email, etc. It seems as if the DNS "woke up" and is getting
> >resolved again.
> >
> >As I mentioned, I've had this "can't resolve DNS" problem for about a
> >month. I've used the above steps twice in the last week and they
> >worked great both times. Previous times, I just left everything
> >alone, chalked it up to a Comcast problem, and it worked again later
> >(usually tried after a couple/few hours).
> >
> >For what it's worth, the two DNS addresses that the router gets from
> >Comcast are:
> >
> >216.148.227.68
> >204.127.202.4
> >
> >All the machines on the network are set to get their IP and DNS info
> >from the router's DHCP server.
> >
> >One thing that seems odd is that the machine I'm on right now is a
> >newly-built machine that was never connected to the older attbi.com
> >network. Still, when I use "ipconfig", it shows:
> >
> >Connection-specific DNS Suffix : attbi.com
> >
> >That seems rather odd to me, so I'm wondering if the router is
> >somehow getting "stale" info when it connects to Comcast. I can't
> >seem to find a list of valid Comcast DNS servers, so I have no idea
> >if the two above addresses are correct/current.
> >
> >Any insight/ideas on what's going on here? I appreciate any help.
> >
> >J
>
> No clue, but then I don't use my router's dhcp service, have manually set
> (four) dns server addresses on all nodes (two for Comcast and two for a
> corporate lan) and manually specified the dns suffix to use on all nodes.
>
> Never lose dns service either...
>
> /daytripper
|
Similar Threads
Linear Mode
