After manually upgrading form nightly build to RC3 on debian, we're slowly approaching the end.
Can someone please post how the /etc/bind/named.conf file should look like, is it just a template file or does it contain all the zone files for the different domains. Is it the all important named.conf file or is it hiding somewhere else ?
Hi
it's the standard named.conf from debian and then added the list of zones by ispcp...
like this (from "// bind Data BEGIN." it's ispcp):
Code:
...
// From the release notes:
// Because many of our users are uncomfortable receiving undelegated answers
// from root or top level domains, other than a few for whom that behaviour
// has been trusted and expected for quite some length of time, we have now
// introduced the "root-delegations-only" feature which applies delegation-only
// logic to all top level domains, and to the root domain. An exception list
// should be specified, including "MUSEUM" and "DE", and any other top level
// domains from whom undelegated responses are expected and trusted.
// root-delegation-only exclude { "DE"; "MUSEUM"; };
include "/etc/bind/named.conf.local";
// bind Data BEGIN.
// dmn [admin.ispcp-dev.xyz.ch] cfg entry BEGIN.
zone "admin.ispcp-dev.xyz.ch" {
type master;
file "/var/cache/bind/admin.ispcp-dev.xyz.ch.db";
notify YES;
};
// dmn [admin.ispcp-dev.xyz.ch] cfg entry END.
// dmn [xn--guide-fra.ch] cfg entry BEGIN.
zone "xn--guide-fra.ch" {
type master;
file "/var/cache/bind/xn--guide-fra.ch.db";
notify YES;
};
// dmn [xn--guide-fra.ch] cfg entry END.
// dmn [{DMN_NAME}] cfg entry BEGIN.
// dmn [{DMN_NAME}] cfg entry END.
// bind Data END.
Thank you for your help, but this is how our named.conf looked like. The error must be somewhere else then.
ok - I don't know what your error is... so I wish you luck...