named.conf revision 71123 
1// $FreeBSD: head/etc/namedb/named.conf 71123 2001-01-16 20:57:18Z ben $
2//
3// Refer to the named(8) man page for details.  If you are ever going
4// to setup a primary server, make sure you've understood the hairy
5// details of how DNS is working.  Even with simple mistakes, you can
6// break connectivity for affected parties, or cause huge amount of
7// useless Internet traffic.
8
9options {
10	directory "/etc/namedb";
11
12// In addition to the "forwarders" clause, you can force your name
13// server to never initiate queries of its own, but always ask its
14// forwarders only, by enabling the following line:
15//
16//      forward only;
17
18// If you've got a DNS server around at your upstream provider, enter
19// its IP address here, and enable the line below.  This will make you
20// benefit from its cache, thus reduce overall DNS traffic in the Internet.
21/*
22	forwarders {
23		127.0.0.1;
24	};
25*/
26	/*
27	 * If there is a firewall between you and nameservers you want
28	 * to talk to, you might need to uncomment the query-source
29	 * directive below.  Previous versions of BIND always asked
30	 * questions using port 53, but BIND 8.1 uses an unprivileged
31	 * port by default.
32	 */
33	// query-source address * port 53;
34
35	/*
36	 * If running in a sandbox, you may have to specify a different
37	 * location for the dumpfile.
38	 */
39	// dump-file "s/named_dump.db";
40};
41
42// Note: the following will be supported in a future release.
43/*
44host { any; } {
45	topology {
46		127.0.0.0/8;
47	};
48};
49*/
50
51// Setting up secondaries is way easier and the rough picture for this
52// is explained below.
53//
54// If you enable a local name server, don't forget to enter 127.0.0.1
55// into your /etc/resolv.conf so this server will be queried first.
56// Also, make sure to enable it in /etc/rc.conf.
57
58zone "." {
59	type hint;
60	file "named.root";
61};
62
63zone "0.0.127.IN-ADDR.ARPA" {
64	type master;
65	file "localhost.rev";
66};
67
68zone "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.INT" {
69	type master;
70	file "localhost.rev";
71};
72
73// NB: Do not use the IP addresses below, they are faked, and only
74// serve demonstration/documentation purposes!
75//
76// Example secondary config entries.  It can be convenient to become
77// a secondary at least for the zone where your own domain is in.  Ask
78// your network administrator for the IP address of the responsible
79// primary.
80//
81// Never forget to include the reverse lookup (IN-ADDR.ARPA) zone!
82// (This is the first bytes of the respective IP address, in reverse
83// order, with ".IN-ADDR.ARPA" appended.)
84//
85// Before starting to setup a primary zone, better make sure you fully
86// understand how DNS and BIND works, however.  There are sometimes
87// unobvious pitfalls.  Setting up a secondary is comparably simpler.
88//
89// NB: Don't blindly enable the examples below. :-)  Use actual names
90// and addresses instead.
91//
92// NOTE!!! FreeBSD can run bind in a sandbox (see named_flags in rc.conf).
93// The directory containing the secondary zones must be write accessible 
94// to bind.  The following sequence is suggested:
95//
96//	mkdir /etc/namedb/s
97//	chown bind.bind /etc/namedb/s
98//	chmod 750 /etc/namedb/s
99
100/*
101zone "domain.com" {
102	type slave;
103	file "s/domain.com.bak";
104	masters {
105		192.168.1.1;
106	};
107};
108
109zone "0.168.192.in-addr.arpa" {
110	type slave;
111	file "s/0.168.192.in-addr.arpa.bak";
112	masters {
113		192.168.1.1;
114	};
115};
116*/
117
118