I have three separate IP ranges, but I would like to keep them under one domain name (without sub-domains).
So far I've created one entry for the zone:
zone "home.net" IN {
type master;
file "home.net.zone";
allow-update { none; };
};

and keep all of my different IP tables in that one zone file.
I would like to have separate files for each IP range. Is that possible to configure?
Leonid

Sure, your reverse and forward domains don't actually have anything directly in common, the would have to be defined as 4 separate zone files (1 forward, 3 reverse).

Aha, sorry, forgot to tell that reverse zones are already separate. I wanted to split forward file into three, but let them be in one domain.
Leonid

ah, well no, that doesn't make sense to do that. the forward zone is about the name, not the addresses.

Here is how my zone file look like. See separate sections down below that represent different subnets. I wanted to separate those into different files so it will be easier to script updates.
If there is no way to split it, can I use INCLUDE operator to do this?

Leonid

# cat home.net.zone
$TTL 86400
home.net. IN SOA winter.home.net. home.net. (
2013051415 ; serial
1D ; refresh
15M ; retry
30D ; expire
1D ; minimum
)
IN NS winter.home.net.
;
; ZONE 10.10.10.0 BEGINS HERE
winter.home.net. IN A 10.10.10.1
winter10 IN CNAME winter
sulaco.home.net. IN A 10.10.10.2
sulaco10 IN CNAME sulaco
; ZONE 10.10.10.0 ENDS HERE
;
; ZONE 10.10.8.0 BEGINS HERE
winter8.home.net. IN A 10.10.8.1
sulaco8.home.net. IN A 10.10.8.2
; ZONE 10.10.8.0 ENDS HERE
;
; Zone 10.10.1.0 BEGINS HERE
winter1.home.net. IN A 10.10.1.1
sulaco1.home.net. IN A 10.10.1.2
; Zone 10.10.1.0 ENDS HERE
;
; Zone 35.15.1.0 BEGINS HERE
winter-wifi.home.net. IN A 35.15.1.1
sulaco-wifi.home.net. IN A 35.15.1.2
; Zone 35.15.1.0 ENDS HERE

$INCLUDE statement does the job, splitting main zone file into subnet files.
Chris, thank you.
Leonid

1 members found this post helpful.

Ahh, good catch. I think that's a fairly recent change in BIND? fundamentally that is outside the scope of the zone file itself, as that's reconstructed to comply with the DNS RFCs. The contents of the zone files are not Bind specific at all, and should be exactly the same as what you'd get from a zone transfer from any other compliant DNS server, but as they do now have the INCLUDE statement I guess you can take a small step away from that standard.