[ale] Setting up BIND

[Chris Ricker]

On Fri, 26 Mar 2004, Alan Dobkin wrote:

> --On Thursday, March 25, 2004 8:21 PM -0500 Chris Fowler 
> <cfowler at outpostsentinel.com> wrote:
> 
> > Now that I have my domain registered and buford.linxdev.com pointing to
> > 66.23.198.2 I want to now configure BIND for all my machines on the
> > 192.168.1.X private.  How can I configure a file for linxdev.com so that
> > it does not get confused with the actual records at:
> 
> If you create a local zone for linxdev.com, then that will be considered
> authoritative for your machines, and they will never contact the actual
> public DNS servers for this domain.  So, you will need to duplicate the
> public entries (i.e. www, smtp, pop, buford, etc.) in your local zone,
> which will have to be updated whenever these IP addresses change.

The best way to do this is with the views (aka "split-dns") feature of BIND.  
Basically, you see where the client is coming from, and serve them different
information based on who they are.

A simple setup is something like:

view "internal" {
        match-clients { 192.168.0.0/16; };

        zone "example.com" IN {
                type master;
                file "internal/db.example";
        };
};

view "external" {
        match-clients { any; };
 
        zone "example.com" IN {
                type master;
                file "external/db.example";
        };
};

People in the 192.168/16 get info from the /var/named/internal/db.example 
file, everyone else gets info from the /var/named/external/db.example 
file....

later,
chris