Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!know!pluto.hemel.bull.co.uk!pmoore
From: pmoore@hemel.bull.co.uk (Paul Moore)
Newsgroups: comp.protocols.tcp-ip.domains
Subject: Re: How to create /etc/hosts from zone
Keywords: hosts
Message-ID: <1990Nov16.175209.5041@hemel.bull.co.uk>
Date: 16 Nov 90 17:52:09 GMT
References: <19523@oolong.la.locus.com> <1667@devildog.att.com> <1990Nov15.185211.876@hemel.bull.co.uk> <1990Nov16.150818.5844@ssd.kodak.com>
Organization: Bull HN UK
Lines: 16

sloey@ssd.kodak.com (Jim Sloey (253-7956)) writes:

>In article <1990Nov15.185211.876@hemel.bull.co.uk> pmoore@hemel.bull.co.uk (Paul Moore) writes:
>>another possibility (ie resolving the problem of keeping hosts for stupid
>>systems and needing a named database) is to keep the /etc/hosts as the
>>master a use a utility to generate the named database from it.        

>I tried this for a while about 3 years ago, but found there was no way to
>keep MX, WKS, and HINFO fields updated without forcing structured comments
>into the host file. 
The hp utility checks for the existance and $include files in the directory
that it is building in (it looks for <domain>.spcl) that allow me to put
MX records for major routes, include cnames etc. MX records for individual
machines are genertaed automatically if you want. HINFO - good point!
I still find it easier to keep a hosts files up to date (maybe I'm getting
old!).