etc/namedb/named.conf

3 // Refer to the named.conf(5) and named(8) man pages, and the documentation
6 // If you are going to set up an authoritative server, make sure you
12 	// All file and path names are relative to the chroot directory,
20 // For named to be accessible to the network, comment this option, specify
25 // use as a local resolver.  To give access to the network, specify
44 // If the 'forwarders' clause is not empty the default is to 'forward first'
45 // which will fall back to sending a query from your local server if the name
47 // force your name server to never initiate queries of its own by enabling the
51 // If you wish to have forwarding configured automatically based on
59 	   query by default in order to dramatically reduce the possibility
60 	   of cache poisoning.  All users are strongly encouraged to utilize
61 	   this feature, and to configure their firewalls to accommodate it.
63 	   AS A LAST RESORT in order to get around a restrictive firewall
65 	   will significantly reduce your ability to withstand cache poisoning
73 // If you enable a local name server, don't forget to enter 127.0.0.1
75 // Also, make sure to enable it in /etc/rc.conf.
83 	2. No spurious traffic will be sent from your network to the roots
84 	3. Greater resilience to any potential root server failure/DDoS
87 	hints file to be sure that an unexpected failure mode has not
120 	for these zones leaving your network and going to the root
123 	2. No spurious traffic will be sent from your network to the roots
322 // Example slave zone config entries.  It can be convenient to become
327 // Do not forget to include the reverse lookup zone!
331 // Before starting to set up a master zone, make sure you fully