Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

controlling DHCP



On Sun, Apr 30, 2006 at 02:14:35PM -0400, James R. Van Zandt wrote:
> 
> >   Again, apologies if I miss anything, but why would you need to change
> >   internal IP addresses just because your external IP address
> >   changed? 
> 
> It's not my own IP I'm thinking of here, but the IP of the DNS server.
> Each of my machines has to be configured to point to one or more DNS
> servers.  The machines using DHCP get their DNS servers and netmasks
> automatically.  For the ones with static IP, I have configured their
> DNS servers manually in /etc/resolv.conf:
>   search comcast.net
>   nameserver 68.87.71.226
>   nameserver 68.87.73.242
> i.e. the ones Comcast provides*.  When those servers move to different
> IPs (as they did within the last few days), my networking breaks, and
> I have to diagnose the problem and update that file.

Tell your machines that the nameserver IP is the internal IP of
the router/DNS server, i.e. 10.0.0.1 or 192.168.0.1 or whatever.

Then it will never change.

-dsr-




BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org