Misc grammar, typo and wording fixes of comments.
PR: docs/41034 Submitted by: Chris Pepper <pepper@rockefeller.edu>
This commit is contained in:
parent
323f66084d
commit
d38c8c5622
Notes:
svn2git
2020-12-20 02:59:44 +00:00
svn path=/head/; revision=110516
@ -1,10 +1,10 @@
|
|||||||
// $FreeBSD$
|
// $FreeBSD$
|
||||||
//
|
//
|
||||||
// Refer to the named.conf(5) and named(8) man pages for details. If
|
// Refer to the named.conf(5) and named(8) man pages for details. If
|
||||||
// you are ever going to setup a primary server, make sure you've
|
// you are ever going to set up a primary server, make sure you
|
||||||
// understood the hairy details of how DNS is working. Even with
|
// understand the hairy details of how DNS works. Even with
|
||||||
// simple mistakes, you can break connectivity for affected parties,
|
// simple mistakes, you can break connectivity for affected parties,
|
||||||
// or cause huge amount of useless Internet traffic.
|
// or cause huge amounts of useless Internet traffic.
|
||||||
|
|
||||||
options {
|
options {
|
||||||
directory "/etc/namedb";
|
directory "/etc/namedb";
|
||||||
@ -49,11 +49,11 @@ host { any; } {
|
|||||||
};
|
};
|
||||||
*/
|
*/
|
||||||
|
|
||||||
// Setting up secondaries is way easier and the rough picture for this
|
// Setting up secondaries is way easier and a rough example for this
|
||||||
// is explained below.
|
// is provided below.
|
||||||
//
|
//
|
||||||
// If you enable a local name server, don't forget to enter 127.0.0.1
|
// If you enable a local name server, don't forget to enter 127.0.0.1
|
||||||
// into your /etc/resolv.conf so this server will be queried first.
|
// first in your /etc/resolv.conf so this server will be queried.
|
||||||
// Also, make sure to enable it in /etc/rc.conf.
|
// Also, make sure to enable it in /etc/rc.conf.
|
||||||
|
|
||||||
zone "." {
|
zone "." {
|
||||||
@ -82,17 +82,17 @@ zone "1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.INT" {
|
|||||||
// serve demonstration/documentation purposes!
|
// serve demonstration/documentation purposes!
|
||||||
//
|
//
|
||||||
// Example secondary config entries. It can be convenient to become
|
// Example secondary config entries. It can be convenient to become
|
||||||
// a secondary at least for the zone where your own domain is in. Ask
|
// a secondary at least for the zone your own domain is in. Ask
|
||||||
// your network administrator for the IP address of the responsible
|
// your network administrator for the IP address of the responsible
|
||||||
// primary.
|
// primary.
|
||||||
//
|
//
|
||||||
// Never forget to include the reverse lookup (IN-ADDR.ARPA) zone!
|
// Never forget to include the reverse lookup (IN-ADDR.ARPA) zone!
|
||||||
// (This is the first bytes of the respective IP address, in reverse
|
// (This is named after the first bytes of the IP address, in reverse
|
||||||
// order, with ".IN-ADDR.ARPA" appended.)
|
// order, with ".IN-ADDR.ARPA" appended.)
|
||||||
//
|
//
|
||||||
// Before starting to setup a primary zone, better make sure you fully
|
// Before starting to set up a primary zone, make sure you fully
|
||||||
// understand how DNS and BIND works, however. There are sometimes
|
// understand how DNS and BIND works. There are sometimes
|
||||||
// unobvious pitfalls. Setting up a secondary is comparably simpler.
|
// non-obvious pitfalls. Setting up a secondary is simpler.
|
||||||
//
|
//
|
||||||
// NB: Don't blindly enable the examples below. :-) Use actual names
|
// NB: Don't blindly enable the examples below. :-) Use actual names
|
||||||
// and addresses instead.
|
// and addresses instead.
|
||||||
|
Loading…
Reference in New Issue
Block a user