named.conf (135961) | named.conf (137182) |
---|---|
1// $FreeBSD: head/etc/namedb/named.conf 135961 2004-09-30 09:57:36Z dougb $ | 1// $FreeBSD: head/etc/namedb/named.conf 137182 2004-11-04 05:24:29Z gshapiro $ |
2// 3// Refer to the named.conf(5) and named(8) man pages, and the documentation 4// in /usr/share/doc/bind9 for more details. 5// 6// If you are going to set up an authoritative server, make sure you 7// understand the hairy details of how DNS works. Even with 8// simple mistakes, you can break connectivity for affected parties, 9// or cause huge amounts of useless Internet traffic. --- 87 unchanged lines hidden (view full) --- 97zone "example.com" { 98 type slave; 99 file "slave/example.com"; 100 masters { 101 192.168.1.1; 102 }; 103}; 104 | 2// 3// Refer to the named.conf(5) and named(8) man pages, and the documentation 4// in /usr/share/doc/bind9 for more details. 5// 6// If you are going to set up an authoritative server, make sure you 7// understand the hairy details of how DNS works. Even with 8// simple mistakes, you can break connectivity for affected parties, 9// or cause huge amounts of useless Internet traffic. --- 87 unchanged lines hidden (view full) --- 97zone "example.com" { 98 type slave; 99 file "slave/example.com"; 100 masters { 101 192.168.1.1; 102 }; 103}; 104 |
105// An example dynamic zone 106key "exampleorgkey" { 107 algorithm hmac-md5; 108 secret "sf87HJqjkqh8ac87a02lla=="; 109}; 110 111zone "example.org" { 112 type master; 113 allow-update { 114 key "exampleorgkey"; 115 }; 116 file "dynamic/example.org"; 117}; 118 |
|
105zone "0.168.192.in-addr.arpa" { 106 type slave; 107 file "slave/0.168.192.in-addr.arpa"; 108 masters { 109 192.168.1.1; 110 }; 111}; 112*/ 113 | 119zone "0.168.192.in-addr.arpa" { 120 type slave; 121 file "slave/0.168.192.in-addr.arpa"; 122 masters { 123 192.168.1.1; 124 }; 125}; 126*/ 127 |