home *** CD-ROM | disk | FTP | other *** search
- X-Gateway-Source-Info: INTERNET
- Path: sparky!uunet!elroy.jpl.nasa.gov!ames!network.ucsd.edu!mvb.saic.com!tgv.com!info-multinet
- Date: 28 AUG 92 00:49:57 GMT
- Newsgroups: vmsnet.networks.tcp-ip.multinet
- X-Return-path: <info-multinet-relay@TGV.COM>
- X-RFC822-From: adelman (Kenneth Adelman) @ TGV.COM
- From: adelman@TGV.COM
- Subject: Re: Clusters and DNS caching
- Organization: The INFO-MULTINET Community
- Message-ID: <2020334828AUG92004957@TGV.COM>
- Nntp-Posting-Host: Mvb.Saic.Com
- Lines: 27
-
- > Given a homogeneous cluster, with Multinet running on all
- > hosts (the easy case)...
-
- > -- Is it plausible to put the DNS cache file,
- > normally multinet:domain-name-service.cache, in the common area and
- > let all of them update it and read from it? Or is the code used for
- > that purpose such that one should keep them separate?
-
- > -- If the caches should be separated, is there any advantage of setting
- > them up as forwarders to each other? And, if so, how would you suggest
- > configuring that for, e.g., a three-host cluster?
-
- > For aesthetic, policy, and administrative reasons, we would rather not
- > make one of the hosts appreciably more equal than the others if this can
- > be avoided.
-
- The DOMAIN-NAME-SERVICE.CACHE file is only the bootstrap
- cache (the information about how to find the root nameservers). This
- isn't ever updated (except by hand) and should normally be left
- in SYS$COMMON.
-
- The "cache" of information is kept in memory and not saved to
- disk. I'd recommend using forwarders which all point at one or
- two master machines to produce a "mega-cache" for your site.
-
- Ken
-