Zonefile Naming Conventions

[Kevin Darcy]

I use the zone name as the zonefile name for all zone except "." of 
course, which I call simply "root".

As for zonefile *directory* conventions, I have a variety of different 
conventions, depending on whether the nameserver instance has multiple 
views, whether or not it's chroot'ed, etc. We've never had enough zones 
that it has made sense to group zonefiles into subdirectories purely for 
filesystem performance reasons, but the number of zones we host is 
growing by leaps and bounds, so I expect I'll have to do that soon...

                                                                         
                                             - Kevin

/dev/rob0 wrote:

>Jeff Hardy wrote:
>  
>
>>I have worked with a number of different Bind configs, and wondered what
>>filenaming conventions people have come up with for zone files, or if
>>there is any kind of standard.  I have never quite settled on one.  I
>>    
>>
>
>My preference is the zone name for forward zones and the IP range for 
>reverse:
>
>zone "zonename.tld"
>{
>     file "zonename.tld";
>     ...
>}
>
>zone "42.168.192.in-addr.arpa"
>{
>     file "192.168.42";
>     ...
>}
>
>On mixed master/slave installs I'm using master and slave 
>subdirectories. Sometimes I use subdirectories for other purposes, 
>perhaps for different domain owners using the sane server.
>  
>