1 // $FreeBSD: src/etc/namedb/named.conf,v 1.6.2.7 2003/02/13 13:16:51 keramida Exp $
3 // Refer to the named.conf(5) and named(8) man pages for details. If
4 // you are ever going to set up a primary server, make sure you
5 // understand the hairy details of how DNS works. Even with
6 // simple mistakes, you can break connectivity for affected parties,
7 // or cause huge amounts of useless Internet traffic.
10 directory "/etc/namedb";
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:
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.
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
33 // query-source address * port 53;
36 * If running in a sandbox, you may have to specify a different
37 * location for the dumpfile.
39 // dump-file "s/named_dump.db";
42 // Note: the following will be supported in a future release.
51 // Setting up secondaries is way easier and a rough example for this
54 // If you enable a local name server, don't forget to enter 127.0.0.1
55 // first in your /etc/resolv.conf so this server will be queried.
56 // Also, make sure to enable it in /etc/rc.conf.
63 zone "0.0.127.IN-ADDR.ARPA" {
69 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" {
71 file "localhost-v6.rev";
74 // RFC 1886 -- deprecated
75 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.INT" {
77 file "localhost-v6.rev";
80 // NB: Do not use the IP addresses below, they are faked, and only
81 // serve demonstration/documentation purposes!
83 // Example secondary config entries. It can be convenient to become
84 // a secondary at least for the zone your own domain is in. Ask
85 // your network administrator for the IP address of the responsible
88 // Never forget to include the reverse lookup (IN-ADDR.ARPA) zone!
89 // (This is named after the first bytes of the IP address, in reverse
90 // order, with ".IN-ADDR.ARPA" appended.)
92 // Before starting to set up a primary zone, make sure you fully
93 // understand how DNS and BIND works. There are sometimes
94 // non-obvious pitfalls. Setting up a secondary is simpler.
96 // NB: Don't blindly enable the examples below. :-) Use actual names
97 // and addresses instead.
99 // NOTE!!! FreeBSD can run bind in a sandbox (see named_flags in rc.conf).
100 // The directory containing the secondary zones must be write accessible
101 // to bind. The following sequence is suggested:
103 // mkdir /etc/namedb/s
104 // chown bind:bind /etc/namedb/s
105 // chmod 750 /etc/namedb/s
110 file "s/domain.com.bak";
116 zone "0.168.192.in-addr.arpa" {
118 file "s/0.168.192.in-addr.arpa.bak";