seperate static and dynamic update zone files?

[Chris Buxton]

It's not possible to separate a single dynamic zone into multiple  
files. (You can do it with static zones using $INCLUDE directives,  
but that doesn't work for dynamic zones.) Here are a few options:

- You can use the sandboxing technique you described, putting the  
dynamic hostnames into a subzone.

- You can use nsupdate instead of freeze/thaw to manage your static  
entries. Just make sure to tune your update-policy statement to allow  
what you want.

- You can use some kind of management system that allows you to edit  
dynamic zones as if they were static zones. There are commercial  
solutions out there, such as one made by my company; there may also  
be FOSS solutions available.

If there are other ways to solve this, I don't know of them.

Chris Buxton
Men & Mice

On Jun 26, 2007, at 3:20 PM, Clenna Lumina wrote:

> I have a (hypothetical) question, which I am curious about (I may some
> day use the answers I get here in the real world, who knows :) )
>
> Lets say I have a local zone for a large corporate or whatever LAN.  
> Say
> local.corp.com is the local-only domain.
>
> Ok, so a hostname of a client system can be mapped to it's assigned IP
> via DHCP (dynamic update.)
>
> Lets say there are some servers on the LAN (mail, dns, http, etc) that
> have static IPs.
>
> In the Bind setup, you would have a zone "local.corp.com" and a
> corresponding zone files (say: type master; file  
> "db.local.corp.com) and
> dynamic updates allowed for the specific IP pool the DHCP'ed clients
> use.
>
> My question is this. Is it possible to have separate files for the  
> main
> static part of the zone, and one for all the dynamic updates? That way
> one could edit the static zone file without having to freeze/thaw, as
> noted in DNS & Bind.
>
> Actually as I was typing this, one possible solution popped into my
> mind, though I'm not sure how well it would work:
>
>    zone "local.corp.com" {
>       type master;
>       file "local.corp.com";
>       ...
>    };
>
>    zone "clients.local.corp.com" {
>       type master;
>       file "clients.local.corp.com";
>       update-policy { grant dhcp.local.corp.com name
> "clients.local.corp.com"; };
>    };
>
> This would effectively give separate files, but only if I want the
> dhcp'ed clients in a subdomain (ie:  
> 10-10-21.clients.local.corp.com) but
> would not work if you wanted, say, dhcp-10-10-21.local.corp.com, which
> is what I want to achieve.
>
> What I'd really find useful is something like:
>
>
>    zone "local.corp.com" {
>       type master;
>       file "local.corp.com";
>       dynamic-file "clients.local.corp.com";
>       update-policy { grant dhcp.local.corp.com name
> "clients.local.corp.com"; };
>       ...
>    };
>
> (And slaves would perhaps just get full end resultant zone when
> transfering.)
>
> Maybe this could be an idea for the next version? (Unless theres  
> already
> a way to do this.)
>
> Thank you.
>
> -- 
> CL
>
>
>