home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!munnari.oz.au!uniwa!craig
- From: craig@ec.uwa.oz.au (Craig Richmond - division)
- Newsgroups: comp.unix.admin
- Subject: Re: DNS/named: Caching vs. Forwarding Server?
- Date: 11 Sep 1992 01:28:01 GMT
- Organization: The University of Westrn Australia
- Lines: 28
- Message-ID: <18osn1INNfu0@uniwa.uwa.edu.au>
- References: <rhoward.716131894@matd>
- NNTP-Posting-Host: decel.ecel.uwa.edu.au
-
- rhoward@matd.gatech.edu (Robert L. Howard) writes:
-
- >The problem is that I don't understand quite the subtle
- >difference between the two. What I desire is that when
- >the DS-1 link is down that I will at least have minimal
- >DNS for those hosts local to me, which would probably
- >be in the cache. (Ideally, I'd also like some way to force
- >some list of hosts into the cache right at boot time so if
- >the DS-1 link goes down 3 minutes later, I will have more
- >than 2 hosts in the cache.)
-
- How about setting yourself up as a primary name server, but put your entry
- as the second name server in the resolv.conf file on all your machines.
- This way it won't go around putting things in the cache left right and
- centre. Only if your normal name server fails a lookup.
-
- You could put the local machines into a cache file. named can be set up
- with a cache file of DNS information to be cached at startup.
-
- I don't know how well this would work and I'm not really in a position to
- test it, so good luck and I hope it works.
-
- Craig
- --
- Craig Richmond. Computer Officer - Dept of Economics (morning) 380 3860
- University of Western Australia Dept of Education (afternoon)
- craig@ecel.uwa.edu.au Dvorak Keyboards RULE!
- "Only users are allowed to make messes on their computers" I.M.VI
-