Ruse, Kevin KPSI on Mon, 22 Sep 2003 09:57:06 -0400 |
My comcast in Bryn Marw fails to connect to google (which is cnamed to 216.239.39.99), while at work my non-comcast connection does connect to that same cname. I have not tried this on a windows machine but unless comcast is doing some really really really fancy filtering, that is not related. So this seems to be solely a comcast issue and not a dns issue. As i wrote this it just started working again, so i'll skip the traceroutes :> Kevin Ruse Kvaerner Philadelphia Shipyard -----Original Message----- From: Art Clemons [mailto:artclemons@aol.com] Sent: Saturday, September 20, 2003 4:46 PM To: plug@lists.phillylinux.org Subject: Re: [PLUG] messed up redhat box > I am in the northeast philadelphia area and I seem to be getting google fine > now. I'm in Mt. Airy, and it still doesn't resolve properly. Of course if I go to http://216.239.37.100/ I get google anyway, so it's not a major problem, it's obviously just a DNS problem. _________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.netisland.net/mailman/listinfo/plug-announce General Discussion -- http://lists.netisland.net/mailman/listinfo/plug _________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.netisland.net/mailman/listinfo/plug-announce General Discussion -- http://lists.netisland.net/mailman/listinfo/plug
|
|