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