1
--- maradns-1.2.12.02/doc/en/source/recursive.ej 2006-03-22 02:00:24.000000000 -0600
2
+++ maradns-1.2.12.03/doc/en/source/recursive.ej 2006-08-15 12:47:01.000000000 -0500
4
They are the best name servers for simple "set and forget" recursive
8
-There are a lot of legitimate objections to the ICANN name servers. I am
9
-not happy that they blocked the existence of the <tt>.xxx</tt> top-level
10
-domain. I also feel that they are too US-centric. We're commenting this
11
-out because religious issues don't belong in a technical document.
16
It is possible, however, to change the root DNS servers used by setting the
18
ipv4_bind_addresses = "localhost"
19
chroot_dir = "/etc/maradns"
20
recursive_acl = "localhost"
21
-ipv4_alias["icann-a"] = "198.41.0.4,"
22
+ipv4_alias["icann-a"] = "198.41.0.4"
23
ipv4_alias["icann-b"] = "192.228.79.201"
24
ipv4_alias["icann-c"] = "192.33.4.12"
25
ipv4_alias["icann-d"] = "128.8.10.90"
29
Replace 192.168.0.1 with the IP of the machine running the recursive MaraDNS;
30
-replace 192.168.0.0/24 (This means "anything which begins with "192.168.0")
31
+replace 192.168.0.0/24 (This means "anything that begins with 192.168.0")
32
with the IP range allowed to access the recursive DNS server.
38
More information on having host names for an internal network is available
39
-in the <A href=authoritative.html#network>network section of the
40
+in the <A href="authoritative.html#network">network section of the
41
authoritative document</A>.
44
--- maradns-1.2.12.02/doc/en/source/glossary.ej 2005-10-03 15:13:46.000000000 -0500
45
+++ maradns-1.2.12.03/doc/en/source/glossary.ej 2006-08-15 12:40:35.000000000 -0500
47
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
50
-<!-- Copyright 2005 Sam Trenholme
51
+<!-- Copyright 2005-2006 Sam Trenholme
58
<A name="authoritative">
59
-<DT>Authoritative DNS server</DT>
60
+<DT><b>Authoritative DNS server</b></DT>
61
<DD>A DNS server which <i>recursive DNS servers</i> contact in order to
62
-<i>resolve</i> a given <i>DNS node</i> </DD>
63
+<i>resolve</i> a given <i>DNS node</i> <p></DD>
67
+<DT><b>DNS node</b></DT>
68
<DD>A name which DNS usually converts in to an IP, such as www.yahoo.com.
69
-Not all DNS nodes have IPs, however.</DD>
70
+Not all DNS nodes have IPs, however.<p></DD>
74
+<DT><b>DNS record</b></DT>
75
<DD>A single piece of DNS data, which can either be data for a DNS node,
76
-or meta-data which DNS uses.</DD>
77
+or meta-data which DNS uses.<p></DD>
81
-<DD>A program which resolves DNS records</DD>
82
+<DT><b>DNS server</b></DT>
83
+<DD>A program which resolves DNS records<p></DD>
86
-<DT>DNS server administrator</DT>
87
+<DT><b>DNS server administrator</b></DT>
88
<DD>A person who manages DNS; setting up DNS servers, changing DNS records,
90
+and what not.<p></DD>
93
-<DT>Domain registry</DT>
94
+<DT><b>Domain registry</b></DT>
95
<DD>A domain registry is a company that allows one to have their
96
<i>authoritative DNS servers</i> be contacted by <i>recursive name
98
+servers</i>. <p></DD>
101
-<DT>Domain suffix</DT>
102
+<DT><b>Domain suffix</b></DT>
103
<DD>The part of the domain which is (usually) after the first dot in a
104
DNS node. The domain suffix for www.yahoo.com, for example, is yahoo.com.
109
-<DT>Domain zone</DT>
110
+<DT><b>Domain zone</b></DT>
111
<DD>A domain zone is a set of one or more DNS nodes. All names in a given
112
-domain zone share the same <i>domain suffix</i>. </DD>
113
+domain zone share the same <i>domain suffix</i>. <p></DD>
118
<DD>A number which a computer connected to the internet has, similiar to a
120
+phone number. <p></DD>
123
-<DT>Internet service provider</DT>
124
+<DT><b>Internet service provider</b></DT>
125
<DD>An internet service provider (or ISP) is a company that offers
126
-access to the internet.</DD>
127
+access to the internet.<p></DD>
130
-<DT>Mail Transport Agent</DT>
131
+<DT><b>Mail Transport Agent</b></DT>
132
<DD>A computer program which accepts incoming SMTP (email) connections,
133
-allowing a server to receive email.</DD>
134
+allowing a server to receive email.<p></DD>
137
-<DT>Recursive DNS server</DT>
138
+<DT><b>Recursive DNS server</b></DT>
139
<DD>A recursive DNS server is a DNS server which contacts other DNS
140
-servers to <i>resolve</i> a given <i>DNS node</i>. </DD>
141
+servers to <i>resolve</i> a given <i>DNS node</i>. <p></DD>
145
+<DT><b>To resolve</b></DT>
146
<DD>To convert a <i>DNS node</i>, such as www.yahoo.com, in
147
-to an IP, such as 10.17.243.32.</DD>
148
+to an IP, such as 10.17.243.32.<p></DD>
152
+<DT><b>To serve</b></DT>
153
<DD>The action of an authoritative DNS server making DNS nodes available
154
-to recursive DNS servers.</DD>
155
+to recursive DNS servers.<p></DD>
158
-<DT>Static IP address</DT>
159
+<DT><b>Static IP address</b></DT>
160
<DD>A static IP address is an IP addresses whose value does not change.
161
-Only some internet service providers offer static IP addresses.</DD>
162
+Only some internet service providers offer static IP addresses.<p></DD>
166
--- maradns-1.2.12.02/doc/en/source/update.ej 2006-03-22 02:00:24.000000000 -0600
167
+++ maradns-1.2.12.03/doc/en/source/update.ej 2006-08-15 13:02:37.000000000 -0500
169
<h1>Table of contents</h1>
171
<li><A href=#1.0>Updating from 1.0 to 1.2</A>
172
-<li><A href=#1.2.03>Updating from 1.2.03 to 1.2.07</A>
173
+<li><A href=#1.2.03>Updating from 1.2.03 to a later 1.2 release</A>
176
+This document is divided in to two parts; anyone upgrading from a
177
+1.0 release to a recent 1.2 release will need to look over both
178
+sections of this document.
181
<h1>Updating from 1.0 to 1.2</h1>
183
@@ -112,10 +116,10 @@
187
-<h1>Updating from 1.2.03 to 1.2.07</h1>
188
+<h1>Updating from 1.2.03 to a later 1.2 release</h1>
190
-There are a few minor changes between the 1.2.03 branch and the 1.2.07
192
+There are a few minor changes between the 1.2.03 branch and later 1.2
193
+releases of MaraDNS:
195
<h3>The special remote queries have been changed</h3>