Date: Wed, 28 May 1997 17:26:31 -0500 (CDT) From: Alec Kloss <alec@d2si.com> To: andrsn@andrsn.stanford.edu (Annelise Anderson) Cc: freebsd-questions@FreeBSD.ORG Subject: Re: DNS cache? Message-ID: <199705282226.RAA02681@d2si.com> In-Reply-To: <Pine.BSI.3.94.970528125023.6115A-100000@andrsn.stanford.edu> from Annelise Anderson at "May 28, 97 12:56:41 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Annelise Anderson is responsible for:
> I agreed in a moment of weakness to take over a small mailing list
> (about 200 names), using majordomo. Outgoing mail to the list is
> rather slow (it takes maybe 20-30 minutes) and I've heard about
> running a "DNS cache" to speed things up. I suppose this works
> by recording the ip addresses associated with the domains when they
> are acquired from (in this case) Stanford's DNS server, so they
> can be looked up locally. Is there a software package for this?
>
> This machine has FreeBSD 2.2.1 installed on it; it's just a
> Pentium 90 with 32 megs ram, but I think it could do better than
> it's been doing....I found bulk_mailer and installed it but haven't
> yet figured out how to set it up.
>
> Thanks--
>
> Annelise
>
>
I belive that you can do this with regular old named(8). I'm not
exactly a named(8) expert, but I suspect you'll need three
configuration files, named something like named.boot, named.cache,
and named.local. Typically there in /etc or a subdirectory of it.
Like everything else there are lots of ways to set it up, so I'll give
you an approximation of how this machine has things arranged.
/etc/named.boot:
directory /etc/namedb
primary 0.0.127.IN-ADDR.ARPA named.local
cache . named.cache
/etc/named.local
@ IN SOA your.host.name alec.d2si.com (
; alec.d2si.com is my email address with @s
; replaced with dots
1 ;Serial
10800 ; Refresh after 3 hours
3600 ; Retry after 1 hour
604800 ; Expire after 1 week
96400 ) ; Minimum TTL 1 day
IN NS 128.101.101.101 ; put your favorite nameserver here
; you can have more than one IN NS line
1 IN PTR localhost.
/etc/named.cache:
. 99999999 IN NS A.ROOT-SERVERS.NET.
99999999 IN NS NS.NASA.GOV.
99999999 IN NS B.ROOT-SERVERS.NET.
99999999 IN NS C.ROOT-SERVERS.NET.
99999999 IN NS D.ROOT-SERVERS.NET.
99999999 IN NS E.ROOT-SERVERS.NET.
99999999 IN NS F.ROOT-SERVERS.NET.
99999999 IN NS G.ROOT-SERVERS.NET.
99999999 IN NS H.ROOT-SERVERS.NET.
;
A.ROOT-SERVERS.NET. 99999999 IN A 198.41.0.4
NS.NASA.GOV. 99999999 IN A 192.52.195.10
B.ROOT-SERVERS.NET. 99999999 IN A 128.9.0.107
C.ROOT-SERVERS.NET. 99999999 IN A 192.33.4.12
D.ROOT-SERVERS.NET. 99999999 IN A 128.8.10.90
E.ROOT-SERVERS.NET. 99999999 IN A 192.203.230.10
F.ROOT-SERVERS.NET. 99999999 IN A 192.5.5.241
G.ROOT-SERVERS.NET. 99999999 IN A 192.112.36.4
H.ROOT-SERVERS.NET. 99999999 IN A 128.63.2.53
I.ROOT-SERVERS.NET. 99999999 IN A 192.36.148.17
The named.cache file is the one I'm least certain about. Anyway, once
you've got these guys set up, start named(8). As I recall, it reads
/etc/named.boot for configuration info. I'll take care of the rest.
Sometime when your machine is idle, run tcpdump(1) on your network
interface and run nslookup(8) and resolve something twice. The first
time, it should generate some network traffic. The second time it
shouldn't. Here's what I got.
> www.american.edu
Server: macbeth.d2si.com
Address: 206.8.31.2
Name: www.american.edu
Address: 147.9.1.10
> www.american.edu
Server: macbeth.d2si.com
Address: 206.8.31.2
Non-authoritative answer:
Name: www.american.edu
Address: 147.9.1.10
The only traffic I saw relateing to these two queries was:
17:04:42.191713 macbeth.d2si.com.domain > rukh.dorsai.org.domain: 32020 (34)
17:04:42.789936 rukh.dorsai.org.domain > macbeth.d2si.com.domain: 32020* 1/4/4 (232)
both of which occured before the second query.
Hope this helps.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199705282226.RAA02681>