diff options
author | keramida <keramida@FreeBSD.org> | 2003-02-07 20:58:38 +0000 |
---|---|---|
committer | keramida <keramida@FreeBSD.org> | 2003-02-07 20:58:38 +0000 |
commit | be3ac9dc01db6968179521188627398bf76c0b0d (patch) | |
tree | 5847d5d9844204154b3be9e70e099a5e4dd56da6 /etc/namedb/named.conf | |
parent | 7684d707568d2124c12b0652e614738cdc88f02b (diff) | |
download | FreeBSD-src-be3ac9dc01db6968179521188627398bf76c0b0d.zip FreeBSD-src-be3ac9dc01db6968179521188627398bf76c0b0d.tar.gz |
Misc grammar, typo and wording fixes of comments.
PR: docs/41034
Submitted by: Chris Pepper <pepper@rockefeller.edu>
Diffstat (limited to 'etc/namedb/named.conf')
-rw-r--r-- | etc/namedb/named.conf | 22 |
1 files changed, 11 insertions, 11 deletions
diff --git a/etc/namedb/named.conf b/etc/namedb/named.conf index c4248d6..c877295 100644 --- a/etc/namedb/named.conf +++ b/etc/namedb/named.conf @@ -1,10 +1,10 @@ // $FreeBSD$ // // 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 -// understood the hairy details of how DNS is working. Even with +// you are ever going to set up a primary server, make sure you +// understand the hairy details of how DNS works. Even with // 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 { directory "/etc/namedb"; @@ -49,11 +49,11 @@ host { any; } { }; */ -// Setting up secondaries is way easier and the rough picture for this -// is explained below. +// Setting up secondaries is way easier and a rough example for this +// is provided below. // // 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. 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! // // 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 // primary. // // 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.) // -// Before starting to setup a primary zone, better make sure you fully -// understand how DNS and BIND works, however. There are sometimes -// unobvious pitfalls. Setting up a secondary is comparably simpler. +// Before starting to set up a primary zone, make sure you fully +// understand how DNS and BIND works. There are sometimes +// non-obvious pitfalls. Setting up a secondary is simpler. // // NB: Don't blindly enable the examples below. :-) Use actual names // and addresses instead. |