multi-domained h2n?

[Kevin Darcy]

Okay, it's time for my sermon again...

If you've already grown to the point of having multiple domains, don't
you think it's probably time to stop using the hosts file as your primary
maintenance point and start using DNS instead? There are numerous tools
out there for maintaining zone files. And if you still have a
_legitimate_ need for hosts files, it's fairly trivial to generate them
from the zone files.


- Kevin

hilgart at my-deja.com wrote:

> Can someone point out the location of a good open source script for
> managing multiple zones on a Unix server?
>
> We are using something written 10(?) years ago which is fairly decent
> but showing its age. The source files look like host tables in the
> location src/hosts.dep.  After editing that file you go up a directory
> and type "make".  It was written with a complex shell script and
> Makefile (obviously).  It's not too hard to hack to support multiple
> domains from multiple host table, but I'd rather start with something
> pre-existing.
>
> We looked at a commercial solution, QIP, but that just seemed like
> complete overkill.  That involves trying to map everything you have
> mastered about DNS to its own terminology.
>
> h2n seems to have a clunky interface - better suited for one-time zone
> creation than regular maintenance via the host table.  I say that
> because of the mandatory arguments.  That's too much typing...
>
> If there's really nothing out there I'll write a general-purpose PERL
> script, perhaps eventually web-enabling it.
>