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 |
On Tue, Oct 02, 2001 at 05:28:07PM -0400, David Kramer wrote: > 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? Yes, sort of. DNS is the protocol, BIND is the implementation most commonly used, and named is the daemon name. > But how does the nameserver know how to lookup names? /etc/resolv.conf? That's what's provided by the caching-nameserver package. The configuration points to the root servers. Your server will do recursive queries of the root servers to get the IP addresses. > My linux box would not itself be using the nameserver running on it, > right? It certainly could, that's up to you. That's what /etc/resolv.conf does. If you put 127.0.0.1 in there as your name server, the linux box will use itself. > Thanks. You're welcome! -- --------------------------------------------------- Derek Martin | Unix/Linux geek ddm at pizzashack.org | GnuPG Key ID: 0x81CFE75D Retrieve my public key at http://pgp.mit.edu - 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. |