home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.protocols.tcp-ip.domains
- Path: sparky!uunet!usc!cs.utexas.edu!qt.cs.utexas.edu!yale.edu!spool.mu.edu!darwin.sura.net!ra!wintermute.phys.psu.edu!atlantis.psu.edu!barr
- From: barr@pop.psu.edu (David Barr)
- Subject: Re: Negative caching
- Message-ID: <??c1Hzvmyb@atlantis.psu.edu>
- Sender: news@atlantis.psu.edu (Usenet)
- Organization: Penn State Population Research Institute
- References: <1ihlanINNlj9@daisy.ee.und.ac.za> <#gb1Hfjgyb@atlantis.psu.edu> <1ii2nsINNnsj@daisy.ee.und.ac.za>
- Distribution: inet
- Date: Thu, 07 Jan 93 22:01:55 GMT
- Lines: 23
-
- In article <1ii2nsINNnsj@daisy.ee.und.ac.za> barrett@daisy.ee.und.ac.za (Alan P Barrett) writes:
- >In article <#gb1Hfjgyb@atlantis.psu.edu>,
- >barr@pop.psu.edu (David Barr) writes:
- >> Hmm. Does this work?
- >
- >No. You can make no assumptions about the validity of the domains
- >between the one you asked about and the one reported in the SOA record in
- >the NXDOMAIN error reply. You know that the intermediate domains don't
- >have SOA records but you don't know if they exist. If you asked for the
- >SOA record for one of these intermediate domains you might get either
- >NOERROR or NXDOMAIN, and until you try it you don't know which it will be.
-
- Right. Which is why I don't do negative caching for intermediate
- domains. (did you not understand my wording or did I miss something?)
-
- To summarize my summary, my suggestion is to cache invalid domains only if
- there are no intermediate domains between the one I asked about and
- the one reported in the SOA record in the NXDOMAIN error reply.
-
- --Dave
- --
- System Administrator, Population Research Institute barr@pop.psu.edu
- What does it profit a man if he gains the whole world, but still runs DOS?
-