| 1 |
On 5/3/06, Christopher E <sensory.access@×××××.com> wrote: |
| 2 |
> # Generated by dhcpcd for interface eth0 |
| 3 |
> domain hsd1.ma.comcast.net. |
| 4 |
> nameserver 68.87.71.226 |
| 5 |
> nameserver 68.87.73.242 |
| 6 |
|
| 7 |
|
| 8 |
Aha! You're on Comcast! |
| 9 |
|
| 10 |
I also have Comcast, and occasionally I have issues where their DNS |
| 11 |
servers will give me the wrong IP for a domain name (happens when |
| 12 |
their automated "You must register to use our system" system gets |
| 13 |
funked up and forgets that I'm a legitimate user) - I get their |
| 14 |
"Please contact us to sign up" redirected page instead. So, try |
| 15 |
copying the URL that emerge is trying to grab, paste it into your |
| 16 |
regular web browser, and see what comes up. If it comes up with a file |
| 17 |
download, then just save that file into /usr/portage/distfiles and |
| 18 |
then that particular emerge should be fine (but you will still |
| 19 |
apparently have a larger issue). If it comes up with the Comcast |
| 20 |
stupidity web page, then you know where your issue lays. I haven't |
| 21 |
even attempted to talk with Comcast tech support about it, as what |
| 22 |
they'll say is "You're using a router? You're running Linux? That |
| 23 |
configuration isn't support, hook a Windows box directly up to the |
| 24 |
cable modem and it should work fine". The way I personally resolved it |
| 25 |
was to use non-Comcast DNS server settings... |
| 26 |
|
| 27 |
HTH- |
| 28 |
|
| 29 |
James |
| 30 |
|
| 31 |
-- |
| 32 |
gentoo-user@g.o mailing list |
Archives