I've solved the nameserver issues by running my own nameserver. I've given up on theirs. sos at zjod.net (Steve Siegfried) writes: > No, not for those specific sites. > > However, a periodic ping of the nameservers that AT&T's DHCP junk points > my box to will usually (in my neighborhood, anyway) show variations on > response time ranging anywhere from between 9 ms all the way up to over > a full second... along with some dropped packets. > > This kinda thing seems worse during "prime time" (11am to around 8pm), > and was especially bad during the worst of the CodeRed attacks. > > It almost looks like AT&T's nameservers are/were undergoing some sort of > packet storm. > > Whenever this gets really bad, I manually add a third (non-AT&T) > nameserver's tcp/ip address to my /etc/resolv.conf file. This seems to > get most of the nslookup glitches. > > -S > > Jon Schewe wrote: > > > > Off and on I'm not able to get to some sites from my cable modem, but if I > > proxy through my work proxy server I can get to the sites. I've confirmed > > this with another AT&T user down the street so it's not just my routing > > table. Anyone else notice this? > > > > Sites that come and go include: > > http://slashdot.org > > http://slashdot.com > > http://www.air1.com > > http://linuxgazette.com > > http://www.csc.calpoly.edu > > > _______________________________________________ > tclug-list mailing list > tclug-list at mn-linux.org > https://mailman.mn-linux.org/mailman/listinfo/tclug-list -- Jon Schewe | http://mtu.net/~jpschewe | jpschewe at mtu.net For I am convinced that neither death nor life, neither angels nor demons, neither the present nor the future, nor any powers, neither height nor depth, nor anything else in all creation, will be able to separate us from the love of God that is in Christ Jesus our Lord. - Romans 8:38-39