Deleted Added
full compact
named.conf (35832) named.conf (35947)
1// $Id: named.boot,v 1.6 1997/05/08 15:23:28 joerg Exp $
2// From: @(#)named.boot 5.1 (Berkeley) 6/30/90
1// $Id: named.conf,v 1.1 1998/05/07 23:42:33 ache Exp $
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:
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//
15//
16// forward only;
17
16// forward only;
17
18// If you've got a DNS server around at your upstream provider, enter
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 /*

--- 12 unchanged lines hidden (view full) ---

39 topology {
40 127.0.0.0/8;
41 };
42};
43*/
44
45// Setting up secondaries is way easier and the rough picture for this
46// is explained below.
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 /*

--- 12 unchanged lines hidden (view full) ---

39 topology {
40 127.0.0.0/8;
41 };
42};
43*/
44
45// Setting up secondaries is way easier and the rough picture for this
46// is explained below.
47//
47//
48// If you enable a local name server, don't forget to enter 127.0.0.1
49// into your /etc/resolv.conf so this server will be queried first.
50// Also, make sure to enable it in /etc/rc.conf.
51
52zone "." {
53 type hint;
54 file "named.root";
55};
56
57zone "0.0.127.IN-ADDR.ARPA" {
58 type master;
59 file "localhost.rev";
60};
61
62// NB: Do not use the IP addresses below, they are faked, and only
63// serve demonstration/documentation purposes!
48// If you enable a local name server, don't forget to enter 127.0.0.1
49// into your /etc/resolv.conf so this server will be queried first.
50// Also, make sure to enable it in /etc/rc.conf.
51
52zone "." {
53 type hint;
54 file "named.root";
55};
56
57zone "0.0.127.IN-ADDR.ARPA" {
58 type master;
59 file "localhost.rev";
60};
61
62// NB: Do not use the IP addresses below, they are faked, and only
63// serve demonstration/documentation purposes!
64//
64//
65// Example secondary config entries. It can be convenient to become
65// Example secondary config entries. It can be convenient to become
66// a secondary at least for the zone where your own domain is in. Ask
67// your network administrator for the IP address of the responsible
68// primary.
69//
66// a secondary at least for the zone where your own domain is in. Ask
67// your network administrator for the IP address of the responsible
68// primary.
69//
70// Never forget to include the reverse lookup (IN-ADDR.ARPA) zone!
70// Never forget to include the reverse lookup (IN-ADDR.ARPA) zone!
71// (This is the first bytes of the respective IP address, in reverse
72// order, with ".IN-ADDR.ARPA" appended.)
73//
71// (This is the first bytes of the respective IP address, in reverse
72// order, with ".IN-ADDR.ARPA" appended.)
73//
74// Before starting to setup a primary zone, better make sure you fully
74// Before starting to setup a primary zone, better make sure you fully
75// understand how DNS and BIND works, however. There are sometimes
75// understand how DNS and BIND works, however. There are sometimes
76// unobvious pitfalls. Setting up a secondary is comparably simpler.
76// unobvious pitfalls. Setting up a secondary is comparably simpler.
77//
77//
78// NB: Don't blindly enable the examples below. :-) Use actual names
78// NB: Don't blindly enable the examples below. :-) Use actual names
79// and addresses instead.
79// and addresses instead.
80
81/*
82zone "domain.com" {
83 type slave;
84 file "domain.com.bak";
85 masters {
86 192.168.1.1;
87 };
88};
89
90zone "0.168.192.in-addr.arpa" {
91 type slave;
92 file "0.168.192.in-addr.arpa.bak";
93 masters {
94 192.168.1.1;
95 };
96};
97*/
98
80
81/*
82zone "domain.com" {
83 type slave;
84 file "domain.com.bak";
85 masters {
86 192.168.1.1;
87 };
88};
89
90zone "0.168.192.in-addr.arpa" {
91 type slave;
92 file "0.168.192.in-addr.arpa.bak";
93 masters {
94 192.168.1.1;
95 };
96};
97*/
98