BLU Discuss list archive

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

controlling DHCP

Subject: controlling DHCP
From: jrvz at comcast.net (James R. Van Zandt)
Date: Sat, 29 Apr 2006 19:30:47 -0400
In-reply-to: <4450D363.4000901@darose.net> (message from David Rosenstrauch on Thu, 27 Apr 2006 10:21:23 -0400)
References: <87u08f5e18.fsf@laymusic.org> <4450D363.4000901@darose.net>

David Rosenstrauch <darose at darose.net> wrote:
>   ... a better solution to the problem is this:  run an 
>   internal DNS server on your LAN, and your problem is solved.

Right.  Simple job for a Linux box, though I've been trying to leave
mine off to save power & wear and tear.  However, my router (Linksys
WRT54GS, firmware v2.07.1) is *already* a Linux box.  I guess I have
to install third party firmware to get DNS running there.  Anybody
have experience with this?

By the way, the other reason to leave local machines DHCP rather than
static, is that when the cable company moves their DNS servers, your
machines get reconfigured automatically.

            - Jim Van Zandt

Follow-Ups:
- controlling DHCP
  - From: david at thekramers.net (David Kramer)
- controlling DHCP
  - From: ward at pong.be (Ward Vandewege)

References:
- controlling DHCP
  - From: lconrad at laymusic.org (Laura Conrad)
- controlling DHCP
  - From: darose at darose.net (David Rosenstrauch)

Prev by Date: Escaping spaces in arguments to shell script
Next by Date: controlling DHCP
Previous by thread: controlling DHCP
Next by thread: controlling DHCP
Index(es):
- Date
- Thread


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

Boston Linux & Unix / webmaster@blu.org