From owner-freebsd-doc Fri Jul 26 20:20:13 2002 Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4022B37B400 for ; Fri, 26 Jul 2002 20:20:03 -0700 (PDT) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7440E43E67 for ; Fri, 26 Jul 2002 20:20:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.4/8.12.4) with ESMTP id g6R3K2JU033234 for ; Fri, 26 Jul 2002 20:20:02 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.4/8.12.4/Submit) id g6R3K2nx033233; Fri, 26 Jul 2002 20:20:02 -0700 (PDT) Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 890B737B400 for ; Fri, 26 Jul 2002 20:14:17 -0700 (PDT) Received: from guest.reppep.com (guest.reppep.com [64.81.19.110]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18B5443E42 for ; Fri, 26 Jul 2002 20:14:17 -0700 (PDT) (envelope-from pepper@guest.reppep.com) Received: by guest.reppep.com (Postfix, from userid 501) id 39FEFFDD8; Fri, 26 Jul 2002 23:14:22 -0400 (EDT) Message-Id: <20020727031422.39FEFFDD8@guest.reppep.com> Date: Fri, 26 Jul 2002 23:14:22 -0400 (EDT) From: Chris Pepper Reply-To: Chris Pepper To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Subject: docs/41034: [PATCH] Typos in /etc/named/named.conf comments Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 41034 >Category: docs >Synopsis: [PATCH] Typos in /etc/named/named.conf comments >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Fri Jul 26 20:20:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Chris Pepper >Release: FreeBSD 4.6-STABLE i386 >Organization: >Environment: System: FreeBSD guest.reppep.com 4.6-STABLE FreeBSD 4.6-STABLE #3: Fri Jul 26 19:51:33 EDT 2002 root@guest.reppep.com:/usr/obj/usr/src/sys/GENERIC i386 >Description: The default named.conf comments are ungramattical. >How-To-Repeat: more /etc/named/named.conf >Fix: Apply this patch. --- named.conf.diff begins here --- --- named.conf Fri Jul 26 23:07:23 2002 +++ named.conf.fixed Fri Jul 26 23:11:25 2002 @@ -1,10 +1,10 @@ // $FreeBSD: src/etc/namedb/named.conf,v 1.6.2.5 2002/02/04 18:24:21 ume Exp $ // // 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"; @@ -16,8 +16,8 @@ // forward only; // If you've got a DNS server around at your upstream provider, enter -// its IP address here, and enable the line below. This will make you -// benefit from its cache, thus reduce overall DNS traffic in the Internet. +// its IP address here, and enable the entry below. This will let you +// benefit from its cache, thus reducing overall DNS traffic on the Internet. /* forwarders { 127.0.0.1; @@ -48,11 +48,11 @@ }; */ -// 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 "." { @@ -74,17 +74,17 @@ // 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. --- named.conf.diff ends here --- >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message