home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!saimiri.primate.wisc.edu!sdd.hp.com!spool.mu.edu!sgiblab!ampex!decwrl!pa.dec.com!vixie
- From: vixie@pa.dec.com (Paul A Vixie)
- Newsgroups: comp.protocols.tcp-ip.domains
- Subject: Re: Does anyone know servers which accept inverse queries?
- Date: 17 Dec 92 11:26:27
- Organization: DEC Network Software Lab
- Lines: 14
- Distribution: inet
- Message-ID: <VIXIE.92Dec17112627@cognition.pa.dec.com>
- References: <199212141825.AA28591@cnam.cnam.fr>
- NNTP-Posting-Host: cognition.pa.dec.com
- In-reply-to: bortzmeyer@cnam.cnam.fr's message of Mon, 14 Dec 92 19:25:46 +0100
-
- Inverse queries are supported by BIND version 4.8.3 and various
- earlier ones; I'm not sure what version they first appeared in.
- My experience with them shows that they are worthless, that they
- consume nontrivial amounts of memory, and that they make the
- name server implementation harder to find and fix bugs in. In
- BIND 4.9, inverse queries are an optional feature. The only
- "production" use of them is in "nslookup", a name server query
- tool, which does an IQUERY on its initial server address rather
- than PTR lookups on them as is done in normal practice.
- --
- Paul Vixie, DEC Network Systems Lab
- Palo Alto, California, USA "Don't be a rebel, or a conformist;
- <vixie@pa.dec.com> decwrl!vixie they're the same thing, anyway. Find
- <paul@vix.com> vixie!paul your own path, and stay on it." -me
-