home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.protocols.tcp-ip.domains
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!news.acns.nwu.edu!nucsrl!pex.eecs.nwu.edu!phil
- From: phil@pex.eecs.nwu.edu (William LeFebvre)
- Subject: Re: Why not automatically do reverse domains?
- Message-ID: <1992Dec11.172920.3011@eecs.nwu.edu>
- Sender: usenet@eecs.nwu.edu (Mr. Usenet)
- Organization: EECS Department, Northwestern University
- References: <NELSON.92Dec8111713@cheetah.clarkson.edu> <CKD.92Dec8180024@loiosh.eff.org>
- Date: Fri, 11 Dec 1992 17:29:20 GMT
- Lines: 31
-
- In article <CKD.92Dec8180024@loiosh.eff.org> ckd@eff.org (Christopher Davis) writes:
- >RN> == Russ Nelson <nelson@sun.soe.clarkson.edu>
- >
- > RN> Why doesn't BIND automatically generate a PTR record for every A
- > RN> record it sees? All the nameserver tools I've seen perform that
- > RN> function, why doesn't BIND? Is there some subtlety that doesn't
- > RN> meet my eye?
- >
- >Having authority for a forward domain does not mean you have authority
- >for the reverse domain. This is the biggest problem.
-
- Another problem is hosts with more than one name. Only one name
- can be canonical, and that is the one that is named in the PTR
- record.
-
- >That said, there probably should be a perl script or something
- >distributed with BIND to generate IN-ADDR.ARPA domains from normal
- >"forward" files...
-
- There is such a tool, but it is not (yet) part of the bind
- distribution. It's called "h2n" and is a perl script written by the
- authors of "DNS and BIND in a nutshell". It converts a file in
- "/etc/hosts" format into the appropriate bind zone files. Off hand, I
- don't know of an archive site that carries it. Cricket? You out
- there?
-
- William LeFebvre
- Computing Facilities Manager and Analyst
- Department of Electrical Engineering and Computer Science
- Northwestern University
- <phil@eecs.nwu.edu>
-