Attachment 23940 Details for Bug 41034 – named.conf.diff

[patch] named.conf.diff

named.conf.diff (text/plain), 2.74 KB, created by Chris Pepper on 2002-07-27 04:20:01 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Chris Pepper

Created: 2002-07-27 04:20:01 UTC

Size: 2.74 KB

patch

obsolete

>--- 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.

Actions: View | Diff

Attachments on bug 41034: 23940