On Fri, 9 Dec 2005 17:08:55 -0700 Richard Fish <[EMAIL PROTECTED]> wrote:
> On 12/9/05, michael higgins <[EMAIL PROTECTED]> wrote: > > I've found that it'll often takes longer to get DNS resolution than content > > over my connection, so I thought a caching DNS server the way to go. With > > that in mind, I installed BIND. > > nscd does this, and is much simpler. It is already installed as part > of glibc. Just do rc-update -a nscd default. Ah. Now, that sounds like the better way to go. > > > From what I understand (right or wrong, IDK), I should only have to look up > > something once, then that info is available locally until I reboot. Or, > > like that... > > It will cache until named is restarted, or the lookup expires. The > lookup expiration time is determined by the authoritative name server > for that domain. > > > So, how do I know if this is doing what I want? If anyone knows the right > > and proper way to do this, I'd appreciate it. > > From one terminal: > > tcpdump dst port 53 > > From another terminal: > > ping -c 4 google.com > ping -c 4 google.com > > If you see domain queries being sent when you do the second ping, then > you are not caching. > Excellent, thanks! I'm emerging tcpdump as I type. Well, the test is the ticket. The thing I needed was to change /etc/resolv.conf. Now it begins to make sense to me. > BTW, if you really want to use named for this, your /etc/resolv.conf > should contain only "nameserver 127.0.0.1". If you are use nscd, then > resolv.conf can be left as is. > Okay. Too bad I didn't ask the list first. It sure looked like BIND was overkill, but I didn't come across another option. Thanks again, -- |\ /| | | ~ ~ | \/ | |---| `|` ? | |ichael | |iggins \^ / michael_higgins[at]iinet[dot]com -- gentoo-user@gentoo.org mailing list
