about the file command

Kevin Darcy kcd at chrysler.com
Wed Feb 9 18:37:04 UTC 2011

On 2/8/2011 9:15 AM, Terry. wrote:
> 2011/2/8 Matus UHLAR - fantomas<uhlar at fantomas.sk>:
>> On 08.02.11 17:40, Terry. wrote:
>>> Can BIND's "file" command referer to more than one zone file?
>>> For example,
>>>        zone "test.nsbeta.info" {
>>>             type master;
>>>             file "a.db";
>>>             file "b.db";
>>>        };
>>> When a record doesn't exist in a.db, BIND will continue to look for it in
>>> b.db.
>> Afaik, no. Why would you want that?
> For views catchall.
> for example, named.conf has three views enabled by default, some users
> have three veiws setup, but some have only two views setup, so I want
> the catchall solution for the the lack of a view.
There is no "default" named.conf. Are you referring to some named.conf 
that was provided in an OS distribution? As part of a third-party DNS 
management tool? Perhaps you need to provide some specifics about your 
particular environment.

The general approach used with views is to include the entries that 
*every* view should see, into each version of the zone(s) in their 
respective views. Yes, this duplicates data and occupies more memory 
than is strictly necessary. If capacity is a problem, you always have 
the option of running separate nameserver instances on separate hardware 
or virtualized OS instances. Views are only a convenience for those who 
have the capacity and the desire to run multiple "logical" nameserver 
instances inside of a single process running in a single OS image.

This cross-view record-level or RRset-level inclusion can be done either 
through $INCLUDE-file chicanery, or by designing/modifying/configuring 
your DNS maintenance system to make and maintain the relevant entries in 

As for selection of views, these are matched in order, so if your last 
view has "match-clients { any; };" (or, if you prefer, 
"match-destinations { any; };", this gives you the "not otherwise 
matched" behavior you seem to be seeking.

                             - Kevin

More information about the bind-users mailing list