named.conf revision 135961 
1// $FreeBSD: head/etc/namedb/named.conf 135961 2004-09-30 09:57:36Z dougb $
2//
3// Refer to the named.conf(5) and named(8) man pages, and the documentation
4// in /usr/share/doc/bind9 for more details.
5//
6// If you are going to set up an authoritative server, make sure you
7// understand the hairy details of how DNS works.  Even with
8// simple mistakes, you can break connectivity for affected parties,
9// or cause huge amounts of useless Internet traffic.
10
11options {
12	directory	"/etc/namedb";
13	pid-file	"/var/run/named/pid";
14	dump-file	"/var/dump/named_dump.db";
15	statistics-file	"/var/stats/named.stats";
16
17// If named is being used only as a local resolver, this is a safe default.
18// For named to be accessible to the network, comment this option, specify
19// the proper IP address, or delete this option.
20	listen-on	{ 127.0.0.1; };
21
22// If you have IPv6 enabled on this system, uncomment this option for
23// use as a local resolver.  To give access to the network, specify
24// an IPv6 address, or the keyword "any".
25//	listen-on-v6	{ ::1; };
26
27// In addition to the "forwarders" clause, you can force your name
28// server to never initiate queries of its own, but always ask its
29// forwarders only, by enabling the following line:
30//
31//      forward only;
32
33// If you've got a DNS server around at your upstream provider, enter
34// its IP address here, and enable the line below.  This will make you
35// benefit from its cache, thus reduce overall DNS traffic in the Internet.
36/*
37	forwarders {
38		127.0.0.1;
39	};
40*/
41	/*
42	 * If there is a firewall between you and nameservers you want
43	 * to talk to, you might need to uncomment the query-source
44	 * directive below.  Previous versions of BIND always asked
45	 * questions using port 53, but BIND versions 8 and later
46	 * use a pseudo-random unprivileged UDP port by default.
47	 */
48	// query-source address * port 53;
49};
50
51// If you enable a local name server, don't forget to enter 127.0.0.1
52// first in your /etc/resolv.conf so this server will be queried.
53// Also, make sure to enable it in /etc/rc.conf.
54
55zone "." {
56	type hint;
57	file "named.root";
58};
59
60zone "0.0.127.IN-ADDR.ARPA" {
61	type master;
62	file "master/localhost.rev";
63};
64
65// RFC 3152
66zone "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" {
67	type master;
68	file "master/localhost-v6.rev";
69};
70
71// RFC 1886 -- deprecated
72zone "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.INT" {
73	type master;
74	file "master/localhost-v6.rev";
75};
76
77// NB: Do not use the IP addresses below, they are faked, and only
78// serve demonstration/documentation purposes!
79//
80// Example slave zone config entries.  It can be convenient to become
81// a slave at least for the zone your own domain is in.  Ask
82// your network administrator for the IP address of the responsible
83// primary.
84//
85// Never forget to include the reverse lookup (IN-ADDR.ARPA) zone!
86// (This is named after the first bytes of the IP address, in reverse
87// order, with ".IN-ADDR.ARPA" appended.)
88//
89// Before starting to set up a primary zone, make sure you fully
90// understand how DNS and BIND works.  There are sometimes
91// non-obvious pitfalls.  Setting up a slave zone is simpler.
92//
93// NB: Don't blindly enable the examples below. :-)  Use actual names
94// and addresses instead.
95
96/*
97zone "example.com" {
98	type slave;
99	file "slave/example.com";
100	masters {
101		192.168.1.1;
102	};
103};
104
105zone "0.168.192.in-addr.arpa" {
106	type slave;
107	file "slave/0.168.192.in-addr.arpa";
108	masters {
109		192.168.1.1;
110	};
111};
112*/
113
114