Ticket #2517 (new good practice)
DNS configuration should be split
|Reported by:||BenBE||Owned by:|
|Priority:||normal||Milestone:||ispCP ω 1.x.0|
|Component:||Config Files||Version:||ispCP ω 1.0.5|
|Severity:||Medium||Keywords:||Bind9, DNS, Configuration|
The configuration for user-domains and custom DNS settings for ispCP should not be written into the main configuration file of bind.
Instead create a separate file for all the customer domains which links in the specific zone configurations, as follows:
/etc/bind9/named.conf --> includes 'named.ispcp.conf'; otherwise remains untouched by ispCP (as the package manager maintains this files) /etc/bind9/named.ispcp.conf --> Contains a list of includes for each (customer) domain /etc/bind9/ispcp/tld.domain.conf --> Zone file configuration domain.tld to load the zone /etc/bind9/ispcp/tld.domain.zone --> Zone file for domain.tld including all subdomains
Regarding the tld.domain notation cf. the discussion regarding splitting up the apache configuration into multiple files instead of one big one (also posted by me).