| named.conf (107254) | named.conf (110516) |
|---|---|
| 1// $FreeBSD: head/etc/namedb/named.conf 107254 2002-11-26 07:55:44Z ume $ | 1// $FreeBSD: head/etc/namedb/named.conf 110516 2003-02-07 20:58:38Z keramida $ |
| 2// 3// Refer to the named.conf(5) and named(8) man pages for details. If | 2// 3// Refer to the named.conf(5) and named(8) man pages for details. If |
| 4// you are ever going to setup a primary server, make sure you've 5// understood the hairy details of how DNS is working. Even with | 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, | 6// simple mistakes, you can break connectivity for affected parties, |
| 7// or cause huge amount of useless Internet traffic. | 7// or cause huge amounts of useless Internet traffic. |
| 8 9options { 10 directory "/etc/namedb"; 11 pid-file "/var/run/named/pid"; 12 13// In addition to the "forwarders" clause, you can force your name 14// server to never initiate queries of its own, but always ask its 15// forwarders only, by enabling the following line: --- 28 unchanged lines hidden (view full) --- 44/* 45host { any; } { 46 topology { 47 127.0.0.0/8; 48 }; 49}; 50*/ 51 | 8 9options { 10 directory "/etc/namedb"; 11 pid-file "/var/run/named/pid"; 12 13// In addition to the "forwarders" clause, you can force your name 14// server to never initiate queries of its own, but always ask its 15// forwarders only, by enabling the following line: --- 28 unchanged lines hidden (view full) --- 44/* 45host { any; } { 46 topology { 47 127.0.0.0/8; 48 }; 49}; 50*/ 51 |
| 52// Setting up secondaries is way easier and the rough picture for this 53// is explained below. | 52// Setting up secondaries is way easier and a rough example for this 53// is provided below. |
| 54// 55// If you enable a local name server, don't forget to enter 127.0.0.1 | 54// 55// If you enable a local name server, don't forget to enter 127.0.0.1 |
| 56// into your /etc/resolv.conf so this server will be queried first. | 56// first in your /etc/resolv.conf so this server will be queried. |
| 57// Also, make sure to enable it in /etc/rc.conf. 58 59zone "." { 60 type hint; 61 file "named.root"; 62}; 63 64zone "0.0.127.IN-ADDR.ARPA" { --- 12 unchanged lines hidden (view full) --- 77 type master; 78 file "localhost-v6.rev"; 79}; 80 81// NB: Do not use the IP addresses below, they are faked, and only 82// serve demonstration/documentation purposes! 83// 84// Example secondary config entries. It can be convenient to become | 57// Also, make sure to enable it in /etc/rc.conf. 58 59zone "." { 60 type hint; 61 file "named.root"; 62}; 63 64zone "0.0.127.IN-ADDR.ARPA" { --- 12 unchanged lines hidden (view full) --- 77 type master; 78 file "localhost-v6.rev"; 79}; 80 81// NB: Do not use the IP addresses below, they are faked, and only 82// serve demonstration/documentation purposes! 83// 84// Example secondary config entries. It can be convenient to become |
| 85// a secondary at least for the zone where your own domain is in. Ask | 85// a secondary at least for the zone your own domain is in. Ask |
| 86// your network administrator for the IP address of the responsible 87// primary. 88// 89// Never forget to include the reverse lookup (IN-ADDR.ARPA) zone! | 86// your network administrator for the IP address of the responsible 87// primary. 88// 89// Never forget to include the reverse lookup (IN-ADDR.ARPA) zone! |
| 90// (This is the first bytes of the respective IP address, in reverse | 90// (This is named after the first bytes of the IP address, in reverse |
| 91// order, with ".IN-ADDR.ARPA" appended.) 92// | 91// order, with ".IN-ADDR.ARPA" appended.) 92// |
| 93// Before starting to setup a primary zone, better make sure you fully 94// understand how DNS and BIND works, however. There are sometimes 95// unobvious pitfalls. Setting up a secondary is comparably simpler. | 93// Before starting to set up a primary zone, make sure you fully 94// understand how DNS and BIND works. There are sometimes 95// non-obvious pitfalls. Setting up a secondary is simpler. |
| 96// 97// NB: Don't blindly enable the examples below. :-) Use actual names 98// and addresses instead. 99// 100// NOTE!!! FreeBSD can run bind in a sandbox (see named_flags in rc.conf). 101// The directory containing the secondary zones must be write accessible 102// to bind. The following sequence is suggested: 103// --- 22 unchanged lines hidden --- | 96// 97// NB: Don't blindly enable the examples below. :-) Use actual names 98// and addresses instead. 99// 100// NOTE!!! FreeBSD can run bind in a sandbox (see named_flags in rc.conf). 101// The directory containing the secondary zones must be write accessible 102// to bind. The following sequence is suggested: 103// --- 22 unchanged lines hidden --- |