Previously, Joel Hammer chose to write: <a very detailed description of his tribulations in getting his server connected to Comcast.net via DHCP>
Bear in mind that I do not run my own DNS server, nor do I host my own e-mail server (yet -- waiting for the comcast crap to work itself out). I do have a domain name, though. Once I determined that my @Home IP was no longer active, I re-booted my freesco router, which was originally configured to connect to @Home via DHCP when I installed it. It connected to Comcast.net with a new IP address using the same account number (aka hostname) that was assigned to my cable modem (which happens to be different from my original account number). I logged into the freesco, ran ifconfig to see what the new IP address is and updated my DNS records at dyndns.org. Four hours later, my hostname, www.thewunders.org (don't go there, it ain't much to look at ;-) ) was back up. My recommendation? If you've got cable internet or DSL, get yourself a router. I'm glad, though, that Joel went through what he did. Because now I know what the nameservers are supposed to be in my resolv.conf file ;-) and I now can use Comcast's servers instead of @Home's. Tim _______________________________________________ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
