db file management

[Kevin Darcy]

I've never really cared for the db.{whatever} convention. I use the name of
the zone for the name of the zonefile, for everything except an internal
root zone, which is just called "root". Makes things real obvious for my
second- and third-stringers...


- Kevin

michael.wilkinson at twcable.com wrote:

> Ok, I had a monumental brain fart... Just maintain then in the same file
> and point to the same file in named.boot for the multiple zones.
>
> Although, I would still be interested in best practices for managing
> multiple db files, etc...
>
> Thanks
>
> michael.wilkinson at twcable.com wrote:
>
> > Hi all-
> >
> > Looking for some ideas on how to manage multiple db files for a range
> > of domains. For example, suppose we are to maintain the following:
> >
> > somezone.com
> > somezone.info
> > somezone.tv
> >
> > Typically,   if I just maintained somezone.info I would create a file
> > called db.somezone for the forward mapping.
> >
> > But now I am to maintain somezone.info and somezone.tv! Yea, can name
> > them what ever we want but we want it manageable;)
> >
> > Looking for best practices when it comes to this... If there is a FAQ
> > or resource let me know. Have to looked at BOG yet but figured all of
> > you gurus would know. Will summarize.
> >
> > thanks-
> >
> > -mike
> >
> >
> >