home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!psgrain!ee.und.ac.za!tplinfm
- From: barrett@daisy.ee.und.ac.za (Alan P Barrett)
- Newsgroups: comp.protocols.tcp-ip.domains
- Subject: Negative caching
- Date: 7 Jan 1993 18:21:43 +0200
- Organization: Dept. Elec. Eng., Univ. Natal, Durban, S. Africa
- Lines: 22
- Distribution: inet
- Message-ID: <1ihlanINNlj9@daisy.ee.und.ac.za>
- References: <BjQPrA-FBh107h@boombox.apana.org.au> <1993Jan7.022756.25843@ssigv.UUCP> <by91Hibayb@atlantis.psu.edu>
- NNTP-Posting-Host: daisy.ee.und.ac.za
-
- In article <by91Hibayb@atlantis.psu.edu>,
- barr@pop.psu.edu (David Barr) writes:
- > 3. The nameserver contacts a root nameserver to find out who "foo.UUCP"
- > is. In the NXDOMAIN response is "how far" the root nameserver got
- > down the tree before it hit the invalid domain. (For example if you
- > query "foo.UUCP" you get ".". If you query "bogus.us" you get
- > ".US". For "bogus.pa.us" you get "pa.us") Thus the local nameserver
- > knows that there is not a ".UUCP" domain, and can therefore cache that
- > information.
-
- The authority records in the NXDOMAIN response tell you the position of
- the nearest zone cut above the nonexistent domain. This is different
- from the nearest valid domain above the nonexistent domain.
-
- For example, if you query for "bogus.in-addr.arpa", you will get an
- NXDOMAIN response with "arpa" in the authority section. You cannot
- conclude that "in-addr.arpa" doesn't exist, but you can conclude that
- there is not a zone cut at "in-addr.arpa".
-
- --apb
- Alan Barrett, Dept. of Electronic Eng., Univ. of Natal, Durban, South Africa
- RFC822: barrett@ee.und.ac.za Bang: m2xenix!undeed!barrett
-