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.
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 the rough picture for this
52 // is explained below.
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.
63 zone "0.0.127.IN-ADDR.ARPA" {
68 // NB: Do not use the IP addresses below, they are faked, and only
69 // serve demonstration/documentation purposes!
71 // Example secondary config entries. It can be convenient to become
72 // a secondary at least for the zone where your own domain is in. Ask
73 // your network administrator for the IP address of the responsible
76 // Never forget to include the reverse lookup (IN-ADDR.ARPA) zone!
77 // (This is the first bytes of the respective IP address, in reverse
78 // order, with ".IN-ADDR.ARPA" appended.)
80 // Before starting to setup a primary zone, better make sure you fully
81 // understand how DNS and BIND works, however. There are sometimes
82 // unobvious pitfalls. Setting up a secondary is comparably simpler.
84 // NB: Don't blindly enable the examples below. :-) Use actual names
85 // and addresses instead.
87 // NOTE!!! FreeBSD runs bind in a sandbox (see named_flags in rc.conf).
88 // The directory containing the secondary zones must be write accessible
89 // to bind. The following sequence is suggested:
91 // mkdir /etc/namedb/s
92 // chown bind.bind /etc/namedb/s
93 // chmod 750 /etc/namedb/s
98 file "s/domain.com.bak";
104 zone "0.168.192.in-addr.arpa" {
106 file "s/0.168.192.in-addr.arpa.bak";