Bind won't start: /etc/named.conf
Dotan Cohen
dotancohen at gmail.com
Tue Sep 28 22:53:09 UTC 2010
On Tue, Sep 28, 2010 at 23:49, Imri Zvik <imriz at inter.net.il> wrote:
> What are you trying to achieve? An empty named.conf file means named will
> use defaults for everything, and will probably just work out-of-the-box (as
> a simple resolver) so you should give more information about the goal and
> problem (including log entries, troubleshooting data etc.).
>
The goal is to for the server to be the second name server for a FQDN.
This is the relevant zone file:
[root at venus ~]# cat /var/named/example.de.hosts
$ORIGIN example.de.
$TTL 86400
example.de. IN SOA example.de. foo.example.de. (
2010092801; Serial - increment me
10800
3600
604800
38400 )
IN NS ns2.example.de.
ns2 IN A x.x.x.168
This is the non-working named.conf that I pieced together from other
working file on other servers:
[root at venus ~# cat /etc/named.conf
options {
directory "/etc";
pid-file "/var/run/named/named.pid";
listen-on {
any;
};
};
zone "." {
type hint;
file "/etc/db.cache";
};
zone "example.de" {
type master;
file "/var/named/example.de.hosts";
};
--
Dotan Cohen
http://gibberish.co.il
http://what-is-what.com
More information about the bind-users
mailing list