1
--- maradns-1.3.02/doc/en/source/recursive.ej 2006-11-24 03:44:29.000000000 -0800
2
+++ maradns-1.3.03/doc/en/source/recursive.ej 2007-01-18 22:39:02.000000000 -0800
7
-<!-- Copyright 2005-2006 Sam Trenholme
8
+<!-- Copyright 2005-2007 Sam Trenholme
13
<li><A href=#upstream>Using other recursive DNS servers</A>
14
<li><A href=#otherroot>Using different root servers</A>
15
<li><A href=#private>Having private host names</A>
16
+<li><A href=#privateauth>Using authoritative records for private names</A>
17
+<li><A href=#privateroot>Private names with custom root servers</A>
18
<li><A href=#custom>Customizing the resolution of some names</A>
22
One may wish to have private host names when running MaraDNS as a recursive
23
name server. These are names that are not attached to the root servers,
24
but will resolve on the recursive name server. For example, it might make
25
-sense to have "router.example.com." resolve to the IP of a router in an
26
+sense to have "router.office." resolve to the IP of a router in an
31
-This is done by taking advantage of the fact that MaraDNS
32
+There are two ways to do this with MaraDNS: By using a custom
33
+root server for only names that end in "office", or by having the
34
+authoritative half of MaraDNS handle custom name resolutions.
38
+<A name="privateauth">
39
+<h2>Using authoritative records for private names</h2>
42
+We can have local names by taking advantage of the fact that
44
can act as both a recursive and authoritative name server on the same IP.
45
MaraDNS first looks up authoritative names before performing recursion.
46
For example, if <tt>www.google.com</tt> is defined in a MaraDNS zone
48
chroot_dir = "/etc/maradns"
49
recursive_acl = "192.168.0.0/24"
51
-csv2["example.com."] = "db.example.com"
52
+csv2["office."] = "db.office"
55
Replace 192.168.0.1 with the IP of the machine running the recursive MaraDNS;
57
in the <A href="authoritative.html#network">network section of the
58
authoritative document</A>.
60
+<A name="privateroot">
61
+<h2>Private names with custom root servers</h2>
64
+MaraDNS, starting with version 1.3.02, can have custom root name servers
65
+that only resolve names in a subtree of the DNS space. In other words,
66
+we can tell MaraDNS to have 192.168.0.7 resolve all names ending in
67
+<tt>office</tt> by having a line like this in one's mararc file:
70
+root_servers["office."] = "192.168.0.7"
73
+Here is how a configuration may look on 192.168.0.1, the recursive
77
+ipv4_bind_addresses = "192.168.0.1"
78
+chroot_dir = "/etc/maradns"
79
+recursive_acl = "192.168.0.0/24"
81
+root_servers["office."] = "192.168.0.7"
84
+And the configuration on 192.168.0.7, the authoritative server:
87
+ipv4_bind_addresses = "192.168.0.7"
88
+chroot_dir = "/etc/maradns"
90
+csv2["office."] = "db.office"
94
<h2>Customizing the resolution of some names</h2>