Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
David Kramer <david at thekramers.net> writes: > On 2 Oct 2001, Derek Atkins wrote: > > > Setting up a caching-only nameserver requires you to: > > 1) install the nameserver binary (this is easy under RedHat and Debian) > > You mean bind? Well, bind is one possibility, yes -- there are others. > > 2) run the nameserver > > 3) set resolv.conf to point to 127.0.0.1 > > > > I would highly recommend you do this. > > But how does the nameserver know how to lookup names? /etc/resolv.conf? The nameserver comes with all the necessary files to lookup names on its own -- in particular, the list of root nameservers. That's all it needs. The file /etc/resolv.conf tells your applications how to resolve names. > My linux box would not itself be using the nameserver running on it, > right? You can run bind without changing /etc/resolv.conf, if you wish (although I don't know WHY you would want to do that). If you don't change /etc/resolv.conf, then the Linux box will not use the local nameserver but your windows boxes (when configured) will use your Linux box's nameserver. > Thanks. -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH warlord at MIT.EDU PGP key available - Subcription/unsubscription/info requests: send e-mail with "subscribe", "unsubscribe", or "info" on the first line of the message body to discuss-request at blu.org (Subject line is ignored).
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |