LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
Reload this Page BIND server not starting, "unknown option 'zone'"
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 09-19-2011, 01:50 PM   #1
StevenW
LQ Newbie
 
Registered: Sep 2011
Posts: 4

Rep: Reputation: Disabled
BIND server not starting, "unknown option 'zone'"

Hi,

My BIND server is not starting, it points me to the config file.

Error message:

WARNING: /etc/namedb/named.conf appears to contain errors which could not be corrected automatically!
/etc/namedb/named.conf:135: unknown option 'zone'
/etc/namedb/named.conf:337: unexpected token near end of file
Please correct these errors manually and rerun /usr/local/cpanel/scripts/fixrndc

This is the config file:

Code:
include "/etc/namedb/rndc.key";

controls {
	inet 127.0.0.1 allow { localhost; } keys { "rndc-key"; };
};

// $FreeBSD: src/etc/namedb/named.conf,v 1.29.2.3.2.1 2010/06/14 02:09:06 kensmith Exp $
//
// Refer to the named.conf(5) and named(8) man pages, and the documentation
// in /usr/share/doc/bind9 for more details.
//
// If you are going to set up an authoritative server, make sure you
// understand the hairy details of how DNS works.  Even with
// simple mistakes, you can break connectivity for affected parties,
// or cause huge amounts of useless Internet traffic.

options {
	// All file and path names are relative to the chroot directory,
	// if any, and should be fully qualified.
	directory	"/etc/namedb/working";
	pid-file	"/var/run/named/pid";
	dump-file	"/var/dump/named_dump.db";
	statistics-file	"/var/stats/named.stats";

// If named is being used only as a local resolver, this is a safe default.
// For named to be accessible to the network, comment this option, specify
// the proper IP address, or delete this option.
	listen-on	{ 127.0.0.1; };

// If you have IPv6 enabled on this system, uncomment this option for
// use as a local resolver.  To give access to the network, specify
// an IPv6 address, or the keyword "any".
//	listen-on-v6	{ ::1; };

// These zones are already covered by the empty zones listed below.
// If you remove the related empty zones below, comment these lines out.
	disable-empty-zone "255.255.255.255.IN-ADDR.ARPA";
	disable-empty-zone "0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA";
	disable-empty-zone "1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA";

// If you've got a DNS server around at your upstream provider, enter
// its IP address here, and enable the line below.  This will make you
// benefit from its cache, thus reduce overall DNS traffic in the Internet.
/*
	forwarders {
		127.0.0.1;
	};
*/

// If the 'forwarders' clause is not empty the default is to 'forward first'
// which will fall back to sending a query from your local server if the name
// servers in 'forwarders' do not have the answer.  Alternatively you can
// force your name server to never initiate queries of its own by enabling the
// following line:
//	forward only;

// If you wish to have forwarding configured automatically based on
// the entries in /etc/resolv.conf, uncomment the following line and
// set named_auto_forward=yes in /etc/rc.conf.  You can also enable
// named_auto_forward_only (the effect of which is described above).
//	include "/etc/namedb/auto_forward.conf";

	/*
	   Modern versions of BIND use a random UDP port for each outgoing
	   query by default in order to dramatically reduce the possibility
	   of cache poisoning.  All users are strongly encouraged to utilize
	   this feature, and to configure their firewalls to accommodate it.

	   AS A LAST RESORT in order to get around a restrictive firewall
	   policy you can try enabling the option below.  Use of this option
	   will significantly reduce your ability to withstand cache poisoning
	   attacks, and should be avoided if at all possible.

	   Replace NNNNN in the example with a number between 49160 and 65530.
	*/
	// query-source address * port NNNNN;
};

// If you enable a local name server, don't forget to enter 127.0.0.1
// first in your /etc/resolv.conf so this server will be queried.
// Also, make sure to enable it in /etc/rc.conf.

// The traditional root hints mechanism. Use this, OR the slave zones below.
zone "." { type hint; file "/etc/namedb/named.root";

/*	Slaving the following zones from the root name servers has some
	significant advantages:
	1. Faster local resolution for your users
	2. No spurious traffic will be sent from your network to the roots
	3. Greater resilience to any potential root server failure/DDoS

	On the other hand, this method requires more monitoring than the
	hints file to be sure that an unexpected failure mode has not
	incapacitated your server.  Name servers that are serving a lot
	of clients will benefit more from this approach than individual
	hosts.  Use with caution.

	To use this mechanism, uncomment the entries below, and comment
	the hint zone above.
*/
/*
zone "." {
	type slave;
	file "/etc/namedb/slave/root.slave";
	masters {
		192.5.5.241;	// F.ROOT-SERVERS.NET.
	};
	notify no;
};
zone "arpa" {
	type slave;
	file "/etc/namedb/slave/arpa.slave";
	masters {
		192.5.5.241;	// F.ROOT-SERVERS.NET.
	};
	notify no;
};
zone "in-addr.arpa" {
	type slave;
	file "/etc/namedb/slave/in-addr.arpa.slave";
	masters {
		192.5.5.241;	// F.ROOT-SERVERS.NET.
	};
	notify no;
};
*/

/*	Serving the following zones locally will prevent any queries
	for these zones leaving your network and going to the root
	name servers.  This has two significant advantages:
	1. Faster local resolution for your users
	2. No spurious traffic will be sent from your network to the roots
*/
// RFC 1912 (and BCP 32 for localhost)
zone "localhost"	{ type master; file "/etc/namedb/master/localhost-reverse.db";
zone "127.in-addr.arpa"	{ type master; file "/etc/namedb/master/localhost-reverse.db";
zone "255.in-addr.arpa"	{ type master; file "/etc/namedb/master/empty.db";

// RFC 1912-style zone for IPv6 localhost address
zone "0.ip6.arpa"	{ type master; file "/etc/namedb/master/localhost-reverse.db";

// "This" Network (RFCs 1912 and 3330)
zone "0.in-addr.arpa"	{ type master; file "/etc/namedb/master/empty.db";

// Private Use Networks (RFC 1918)
zone "10.in-addr.arpa"	   { type master; file "/etc/namedb/master/empty.db";
zone "16.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";
zone "17.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";
zone "18.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";
zone "19.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";
zone "20.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";
zone "21.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";
zone "22.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";
zone "23.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";
zone "24.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";
zone "25.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";
zone "26.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";
zone "27.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";
zone "28.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";
zone "29.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";
zone "30.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";
zone "31.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";
zone "168.192.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";

// Link-local/APIPA (RFCs 3330 and 3927)
zone "254.169.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";

// TEST-NET-[1-3] for Documentation (RFC 5737)
zone "2.0.192.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";
zone "100.51.198.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";
zone "113.0.203.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";

// IPv6 Range for Documentation (RFC 3849)
zone "0.0.0.0.0.0.0.0.8.b.d.0.1.0.0.2.ip6.arpa" { type master; file "/etc/namedb/master/empty.db";

// Domain Names for Documentation and Testing (BCP 32)
zone "test" { type master; file "/etc/namedb/master/empty.db";
zone "example" { type master; file "/etc/namedb/master/empty.db";
zone "invalid" { type master; file "/etc/namedb/master/empty.db";
zone "example.com" { type master; file "/etc/namedb/master/empty.db";
zone "example.net" { type master; file "/etc/namedb/master/empty.db";
zone "example.org" { type master; file "/etc/namedb/master/empty.db";

// Router Benchmark Testing (RFC 3330)
zone "18.198.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";
zone "19.198.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";

// IANA Reserved - Old Class E Space
zone "240.in-addr.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "241.in-addr.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "242.in-addr.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "243.in-addr.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "244.in-addr.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "245.in-addr.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "246.in-addr.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "247.in-addr.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "248.in-addr.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "249.in-addr.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "250.in-addr.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "251.in-addr.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "252.in-addr.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "253.in-addr.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "254.in-addr.arpa"	{ type master; file "/etc/namedb/master/empty.db";

// IPv6 Unassigned Addresses (RFC 4291)
zone "1.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "3.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "4.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "5.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "6.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "7.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "8.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "9.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "a.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "b.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "c.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "d.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "e.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "0.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "1.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "2.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "3.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "4.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "5.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "6.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "7.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "8.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "9.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "a.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "b.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "0.e.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "1.e.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "2.e.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "3.e.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "4.e.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "5.e.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "6.e.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "7.e.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";

// IPv6 ULA (RFC 4193)
zone "c.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "d.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";

// IPv6 Link Local (RFC 4291)
zone "8.e.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "9.e.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "a.e.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "b.e.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";

// IPv6 Deprecated Site-Local Addresses (RFC 3879)
zone "c.e.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "d.e.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "e.e.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";
zone "f.e.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";

// IP6.INT is Deprecated (RFC 4159)
zone "ip6.int"		{ type master; file "/etc/namedb/master/empty.db";

// NB: Do not use the IP addresses below, they are faked, and only
// serve demonstration/documentation purposes!
//
// Example slave zone config entries.  It can be convenient to become
// a slave at least for the zone your own domain is in.  Ask
// your network administrator for the IP address of the responsible
// master name server.
//
// Do not forget to include the reverse lookup zone!
// This is named after the first bytes of the IP address, in reverse
// order, with ".IN-ADDR.ARPA" appended, or ".IP6.ARPA" for IPv6.
//
// Before starting to set up a master zone, make sure you fully
// understand how DNS and BIND work.  There are sometimes
// non-obvious pitfalls.  Setting up a slave zone is usually simpler.
//
// NB: Don't blindly enable the examples below. :-)  Use actual names
// and addresses instead.

/* An example dynamic zone
key "exampleorgkey" {
	algorithm hmac-md5;
	secret "sf87HJqjkqh8ac87a02lla==";
};
zone "example.org" {
	type master;
	allow-update {
		key "exampleorgkey";
	};
	file "/etc/namedb/dynamic/example.org";
};
*/

/* Example of a slave reverse zone
zone "1.168.192.in-addr.arpa" {
	type slave;
	file "/etc/namedb/slave/1.168.192.in-addr.arpa";
	masters {
		192.168.1.1;
	};
};
*/

};

zone "amvserver.net" {
	type master;
	file "/etc/namedb/working/amvserver.net.db";
};


zone "amvserver.net" {
	type master;
	file "/etc/namedb/working/amvserver.net.db";
};
Does anyone know how to fix this? Ive been googling for the fix and it says something about wrong brackets in the file but I cant seem to find the problem around rules 135 and 337..
 
Old 09-19-2011, 02:20 PM   #2
bathory
LQ Guru
 
Registered: Jun 2004
Location: Piraeus
Distribution: Slackware
Posts: 13,229
Blog Entries: 1

Rep: Reputation: 2083Reputation: 2083Reputation: 2083Reputation: 2083Reputation: 2083Reputation: 2083Reputation: 2083Reputation: 2083Reputation: 2083Reputation: 2083Reputation: 2083
It's:
Quote:
zone "." { type hint; file "/etc/namedb/named.root";
that does not have a closing bracket

Regards
 
Old 09-19-2011, 02:29 PM   #3
StevenW
LQ Newbie
 
Registered: Sep 2011
Posts: 4

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by bathory View Post
It's:
that does not have a closing bracket

Regards
Thank for the fast reply, im still having errors after fixing it..

/etc/namedb/named.conf:135: missing ';' before 'include'
/etc/namedb/named.conf:151: 'options' redefined near 'options'
 
Old 09-19-2011, 04:05 PM   #4
bathory
LQ Guru
 
Registered: Jun 2004
Location: Piraeus
Distribution: Slackware
Posts: 13,229
Blog Entries: 1

Rep: Reputation: 2083Reputation: 2083Reputation: 2083Reputation: 2083Reputation: 2083Reputation: 2083Reputation: 2083Reputation: 2083Reputation: 2083Reputation: 2083Reputation: 2083
Oups after that one, you have tons of similar errors!!!
Every line like where you define a zone, e.g.
Quote:
Quote:
zone "10.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";
should end up with a closing bracket
Code:

	
Code:

	
zone "10.in-addr.arpa"     { type master; file "/etc/namedb/master/empty.db";};
Cheers
 
Old 09-19-2011, 04:52 PM   #5
StevenW
LQ Newbie
 
Registered: Sep 2011
Posts: 4

Original Poster
Rep: Reputation: Disabled
It still does not start... :-(

named has failed, please contact the sysadmin (result was "named is not running").
Sep 19 21:50:08 server1 named[27546]: starting BIND 9.6.2-P2 -u bind -c /etc/namedb/named.conf
Sep 19 21:50:08 server1 named[27546]: built with '--prefix=/usr' '--infodir=/usr/share/info' '--mandir=/usr/share/man' '--enable-threads' '--disable-ipv6' '--enable-getifaddrs' '--disable-linux-caps' '--with-openssl=/usr' '--with-randomdev=/dev/random' '--without-idn' '--without-libxml2'
Sep 19 21:50:08 server1 named[27546]: /etc/namedb/named.conf:135: missing ';' before 'include'
Sep 19 21:50:08 server1 named[27546]: /etc/namedb/named.conf:151: 'options' redefined near 'options'
Sep 19 21:50:08 server1 named[27546]: loading configuration: already exists
Sep 19 21:50:08 server1 named[27546]: exiting (due to fatal error)



Code:
include "/etc/namedb/rndc.key";

controls {
	inet 127.0.0.1 allow { localhost; } keys { "rndc-key"; };
};

// $FreeBSD: src/etc/namedb/named.conf,v 1.29.2.3.2.1 2010/06/14 02:09:06 kensmith Exp $
//
// Refer to the named.conf(5) and named(8) man pages, and the documentation
// in /usr/share/doc/bind9 for more details.
//
// If you are going to set up an authoritative server, make sure you
// understand the hairy details of how DNS works.  Even with
// simple mistakes, you can break connectivity for affected parties,
// or cause huge amounts of useless Internet traffic.

options {
	// All file and path names are relative to the chroot directory,
	// if any, and should be fully qualified.
	directory	"/etc/namedb/working";
	pid-file	"/var/run/named/pid";
	dump-file	"/var/dump/named_dump.db";
	statistics-file	"/var/stats/named.stats";

// If named is being used only as a local resolver, this is a safe default.
// For named to be accessible to the network, comment this option, specify
// the proper IP address, or delete this option.
	listen-on	{ 127.0.0.1; };

// If you have IPv6 enabled on this system, uncomment this option for
// use as a local resolver.  To give access to the network, specify
// an IPv6 address, or the keyword "any".
//	listen-on-v6	{ ::1; };

// These zones are already covered by the empty zones listed below.
// If you remove the related empty zones below, comment these lines out.
	disable-empty-zone "255.255.255.255.IN-ADDR.ARPA";
	disable-empty-zone "0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA";
	disable-empty-zone "1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA";

// If you've got a DNS server around at your upstream provider, enter
// its IP address here, and enable the line below.  This will make you
// benefit from its cache, thus reduce overall DNS traffic in the Internet.
/*
	forwarders {
		127.0.0.1;
	};
*/

// If the 'forwarders' clause is not empty the default is to 'forward first'
// which will fall back to sending a query from your local server if the name
// servers in 'forwarders' do not have the answer.  Alternatively you can
// force your name server to never initiate queries of its own by enabling the
// following line:
//	forward only;

// If you wish to have forwarding configured automatically based on
// the entries in /etc/resolv.conf, uncomment the following line and
// set named_auto_forward=yes in /etc/rc.conf.  You can also enable
// named_auto_forward_only (the effect of which is described above).
//	include "/etc/namedb/auto_forward.conf";

	/*
	   Modern versions of BIND use a random UDP port for each outgoing
	   query by default in order to dramatically reduce the possibility
	   of cache poisoning.  All users are strongly encouraged to utilize
	   this feature, and to configure their firewalls to accommodate it.

	   AS A LAST RESORT in order to get around a restrictive firewall
	   policy you can try enabling the option below.  Use of this option
	   will significantly reduce your ability to withstand cache poisoning
	   attacks, and should be avoided if at all possible.

	   Replace NNNNN in the example with a number between 49160 and 65530.
	*/
	// query-source address * port NNNNN;
};

// If you enable a local name server, don't forget to enter 127.0.0.1
// first in your /etc/resolv.conf so this server will be queried.
// Also, make sure to enable it in /etc/rc.conf.

// The traditional root hints mechanism. Use this, OR the slave zones below.
zone "." { type hint; file "/etc/namedb/named.root"; }

/*	Slaving the following zones from the root name servers has some
	significant advantages:
	1. Faster local resolution for your users
	2. No spurious traffic will be sent from your network to the roots
	3. Greater resilience to any potential root server failure/DDoS

	On the other hand, this method requires more monitoring than the
	hints file to be sure that an unexpected failure mode has not
	incapacitated your server.  Name servers that are serving a lot
	of clients will benefit more from this approach than individual
	hosts.  Use with caution.

	To use this mechanism, uncomment the entries below, and comment
	the hint zone above.
*/
/*
zone "." {
	type slave;
	file "/etc/namedb/slave/root.slave";
	masters {
		192.5.5.241;	// F.ROOT-SERVERS.NET.
	};
	notify no;
};
zone "arpa" {
	type slave;
	file "/etc/namedb/slave/arpa.slave";
	masters {
		192.5.5.241;	// F.ROOT-SERVERS.NET.
	};
	notify no;
};
zone "in-addr.arpa" {
	type slave;
	file "/etc/namedb/slave/in-addr.arpa.slave";
	masters {
		192.5.5.241;	// F.ROOT-SERVERS.NET.
	};
	notify no;
};
*/

/*	Serving the following zones locally will prevent any queries
	for these zones leaving your network and going to the root
	name servers.  This has two significant advantages:
	1. Faster local resolution for your users
	2. No spurious traffic will be sent from your network to the roots
*/
// RFC 1912 (and BCP 32 for localhost)
include "/etc/namedb/rndc.key";

controls {
	inet 127.0.0.1 allow { localhost; } keys { "rndc-key"; };
};

// $FreeBSD: src/etc/namedb/named.conf,v 1.29.2.3.2.1 2010/06/14 02:09:06 kensmith Exp $
//
// Refer to the named.conf(5) and named(8) man pages, and the documentation
// in /usr/share/doc/bind9 for more details.
//
// If you are going to set up an authoritative server, make sure you
// understand the hairy details of how DNS works.  Even with
// simple mistakes, you can break connectivity for affected parties,
// or cause huge amounts of useless Internet traffic.

options {
	// All file and path names are relative to the chroot directory,
	// if any, and should be fully qualified.
	directory	"/etc/namedb/working";
	pid-file	"/var/run/named/pid";
	dump-file	"/var/dump/named_dump.db";
	statistics-file	"/var/stats/named.stats";

// If named is being used only as a local resolver, this is a safe default.
// For named to be accessible to the network, comment this option, specify
// the proper IP address, or delete this option.
	listen-on	{ 127.0.0.1; };

// If you have IPv6 enabled on this system, uncomment this option for
// use as a local resolver.  To give access to the network, specify
// an IPv6 address, or the keyword "any".
//	listen-on-v6	{ ::1; };

// These zones are already covered by the empty zones listed below.
// If you remove the related empty zones below, comment these lines out.
	disable-empty-zone "255.255.255.255.IN-ADDR.ARPA";
	disable-empty-zone "0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA";
	disable-empty-zone "1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA";

// If you've got a DNS server around at your upstream provider, enter
// its IP address here, and enable the line below.  This will make you
// benefit from its cache, thus reduce overall DNS traffic in the Internet.
/*
	forwarders {
		127.0.0.1;
	};
*/

// If the 'forwarders' clause is not empty the default is to 'forward first'
// which will fall back to sending a query from your local server if the name
// servers in 'forwarders' do not have the answer.  Alternatively you can
// force your name server to never initiate queries of its own by enabling the
// following line:
//	forward only;

// If you wish to have forwarding configured automatically based on
// the entries in /etc/resolv.conf, uncomment the following line and
// set named_auto_forward=yes in /etc/rc.conf.  You can also enable
// named_auto_forward_only (the effect of which is described above).
//	include "/etc/namedb/auto_forward.conf";

	/*
	   Modern versions of BIND use a random UDP port for each outgoing
	   query by default in order to dramatically reduce the possibility
	   of cache poisoning.  All users are strongly encouraged to utilize
	   this feature, and to configure their firewalls to accommodate it.

	   AS A LAST RESORT in order to get around a restrictive firewall
	   policy you can try enabling the option below.  Use of this option
	   will significantly reduce your ability to withstand cache poisoning
	   attacks, and should be avoided if at all possible.

	   Replace NNNNN in the example with a number between 49160 and 65530.
	*/
	// query-source address * port NNNNN;
};

// If you enable a local name server, don't forget to enter 127.0.0.1
// first in your /etc/resolv.conf so this server will be queried.
// Also, make sure to enable it in /etc/rc.conf.

// The traditional root hints mechanism. Use this, OR the slave zones below.
zone "." { type hint; file "/etc/namedb/named.root"; }

/*	Slaving the following zones from the root name servers has some
	significant advantages:
	1. Faster local resolution for your users
	2. No spurious traffic will be sent from your network to the roots
	3. Greater resilience to any potential root server failure/DDoS

	On the other hand, this method requires more monitoring than the
	hints file to be sure that an unexpected failure mode has not
	incapacitated your server.  Name servers that are serving a lot
	of clients will benefit more from this approach than individual
	hosts.  Use with caution.

	To use this mechanism, uncomment the entries below, and comment
	the hint zone above.
*/
/*
zone "." {
	type slave;
	file "/etc/namedb/slave/root.slave";
	masters {
		192.5.5.241;	// F.ROOT-SERVERS.NET.
	};
	notify no;
};
zone "arpa" {
	type slave;
	file "/etc/namedb/slave/arpa.slave";
	masters {
		192.5.5.241;	// F.ROOT-SERVERS.NET.
	};
	notify no;
};
zone "in-addr.arpa" {
	type slave;
	file "/etc/namedb/slave/in-addr.arpa.slave";
	masters {
		192.5.5.241;	// F.ROOT-SERVERS.NET.
	};
	notify no;
};
*/

/*	Serving the following zones locally will prevent any queries
	for these zones leaving your network and going to the root
	name servers.  This has two significant advantages:
	1. Faster local resolution for your users
	2. No spurious traffic will be sent from your network to the roots
*/
// RFC 1912 (and BCP 32 for localhost)
zone "localhost"	{ type master; file "/etc/namedb/master/localhost-reverse.db";};
zone "127.in-addr.arpa"	{ type master; file "/etc/namedb/master/localhost-reverse.db";};
zone "255.in-addr.arpa"	{ type master; file "/etc/namedb/master/empty.db";};

// RFC 1912-style zone for IPv6 localhost address
zone "0.ip6.arpa"	{ type master; file "/etc/namedb/master/localhost-reverse.db";};

// "This" Network (RFCs 1912 and 3330)
zone "0.in-addr.arpa"	{ type master; file "/etc/namedb/master/empty.db";};

// Private Use Networks (RFC 1918)
zone "10.in-addr.arpa"	   { type master; file "/etc/namedb/master/empty.db";};
zone "16.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";};
zone "17.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";};
zone "18.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";};
zone "19.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";};
zone "20.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";};
zone "21.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";};
zone "22.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";};
zone "23.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";};
zone "24.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";};
zone "25.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";};
zone "26.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";};
zone "27.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";};
zone "28.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";};
zone "29.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";};
zone "30.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";};
zone "31.172.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";};
zone "168.192.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";};

// Link-local/APIPA (RFCs 3330 and 3927)
zone "254.169.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";};

// TEST-NET-[1-3] for Documentation (RFC 5737)
zone "2.0.192.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";};
zone "100.51.198.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";};
zone "113.0.203.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";};

// IPv6 Range for Documentation (RFC 3849)
zone "0.0.0.0.0.0.0.0.8.b.d.0.1.0.0.2.ip6.arpa" { type master; file "/etc/namedb/master/empty.db";};

// Domain Names for Documentation and Testing (BCP 32)
zone "test" { type master; file "/etc/namedb/master/empty.db";};
zone "example" { type master; file "/etc/namedb/master/empty.db";};
zone "invalid" { type master; file "/etc/namedb/master/empty.db";};
zone "example.com" { type master; file "/etc/namedb/master/empty.db";};
zone "example.net" { type master; file "/etc/namedb/master/empty.db";};
zone "example.org" { type master; file "/etc/namedb/master/empty.db";};

// Router Benchmark Testing (RFC 3330)
zone "18.198.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";};
zone "19.198.in-addr.arpa" { type master; file "/etc/namedb/master/empty.db";};

// IANA Reserved - Old Class E Space
zone "240.in-addr.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "241.in-addr.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "242.in-addr.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "243.in-addr.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "244.in-addr.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "245.in-addr.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "246.in-addr.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "247.in-addr.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "248.in-addr.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "249.in-addr.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "250.in-addr.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "251.in-addr.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "252.in-addr.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "253.in-addr.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "254.in-addr.arpa"	{ type master; file "/etc/namedb/master/empty.db";};

// IPv6 Unassigned Addresses (RFC 4291)
zone "1.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "3.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "4.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "5.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "6.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "7.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "8.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "9.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "a.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "b.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "c.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "d.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "e.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "0.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "1.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "2.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "3.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "4.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "5.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "6.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "7.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "8.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "9.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "a.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "b.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "0.e.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "1.e.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "2.e.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "3.e.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "4.e.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "5.e.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "6.e.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "7.e.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};

// IPv6 ULA (RFC 4193)
zone "c.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "d.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};

// IPv6 Link Local (RFC 4291)
zone "8.e.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "9.e.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "a.e.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "b.e.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};

// IPv6 Deprecated Site-Local Addresses (RFC 3879)
zone "c.e.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "d.e.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "e.e.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};
zone "f.e.f.ip6.arpa"	{ type master; file "/etc/namedb/master/empty.db";};

// IP6.INT is Deprecated (RFC 4159)
zone "ip6.int"		{ type master; file "/etc/namedb/master/empty.db";};

// NB: Do not use the IP addresses below, they are faked, and only
// serve demonstration/documentation purposes!
//
// Example slave zone config entries.  It can be convenient to become
// a slave at least for the zone your own domain is in.  Ask
// your network administrator for the IP address of the responsible
// master name server.
//
// Do not forget to include the reverse lookup zone!
// This is named after the first bytes of the IP address, in reverse
// order, with ".IN-ADDR.ARPA" appended, or ".IP6.ARPA" for IPv6.
//
// Before starting to set up a master zone, make sure you fully
// understand how DNS and BIND work.  There are sometimes
// non-obvious pitfalls.  Setting up a slave zone is usually simpler.
//
// NB: Don't blindly enable the examples below. :-)  Use actual names
// and addresses instead.

/* An example dynamic zone
key "exampleorgkey" {
	algorithm hmac-md5;
	secret "sf87HJqjkqh8ac87a02lla==";
};
zone "example.org" {
	type master;
	allow-update {
		key "exampleorgkey";
	};
	file "/etc/namedb/dynamic/example.org";
};
*/

/* Example of a slave reverse zone
zone "1.168.192.in-addr.arpa" {
	type slave;
	file "/etc/namedb/slave/1.168.192.in-addr.arpa";
	masters {
		192.168.1.1;
	};
};
*/

zone "stevenw.net" {
	type master;
	file "/etc/namedb/working/stevenw.net.db";
};

zone "amvserver.net" {
	type master;
	file "/etc/namedb/working/amvserver.net.db";
};



zone "stevenw.net" {
	type master;
	file "/etc/namedb/working/stevenw.net.db";
};


zone "amvserver.net" {
	type master;
	file "/etc/namedb/working/amvserver.net.db";
};


zone "stevenw.net" {
	type master;
	file "/etc/namedb/working/stevenw.net.db";
};


zone "amvserver.net" {
	type master;
	file "/etc/namedb/working/amvserver.net.db";
};
 
Old 09-19-2011, 05:35 PM   #6
bathory
LQ Guru
 
Registered: Jun 2004
Location: Piraeus
Distribution: Slackware
Posts: 13,229
Blog Entries: 1

Rep: Reputation: 2083Reputation: 2083Reputation: 2083Reputation: 2083Reputation: 2083Reputation: 2083Reputation: 2083Reputation: 2083Reputation: 2083Reputation: 2083Reputation: 2083
Quote:
zone "." { type hint; file "/etc/namedb/named.root"; }
Miss the trailing ;
You can use
Code:
named-checkconf /etc/namedb/named.conf
to check named.conf syntax

Regards
 
Old 09-19-2011, 06:27 PM   #7
StevenW
LQ Newbie
 
Registered: Sep 2011
Posts: 4

Original Poster
Rep: Reputation: Disabled
Found my fails I guess, there where a lot more things wrong, options was defined double. Guess the auto config was an epic fail.

Thanks for your help guys!
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] BIND and Unknown RR type "server" riganta Linux - Server 7 04-20-2011 06:41 AM
How do I import bind ".hosts" files into another BIND server chantman Linux - Software 0 06-30-2006 11:51 AM
"ftp: u: unknown option" when script runs through VNC viewer Fillys6 Linux - Networking 7 12-22-2005 07:11 PM
rpm -bp command not working says "-bp: unknown option" Niceman2005 Linux - Software 2 11-08-2004 01:36 AM
dns named.conf: "view" unknown option rioguia Linux - Networking 16 11-02-2004 11:04 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 04:32 PM.

Contact Us - Advertising Info - Rules - Privacy - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -
Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration