1
diff -ur maradns-1.2.12.02.orig/doc/en/source/faq.embed maradns-1.2.12.02/doc/en/source/faq.embed
2
--- maradns-1.2.12.02.orig/doc/en/source/faq.embed 2006-08-10 00:07:34.000000000 -0500
3
+++ maradns-1.2.12.02/doc/en/source/faq.embed 2006-08-10 00:16:40.000000000 -0500
6
<H2>13. I feel that XXX feature should be added to MaraDNS</H2>
8
-There are currently no plans to implement new features in MaraDNS. The
9
-reason for this is because, bottom line, MaraDNS has failed to make my
10
-resume impressive enough for me to easily get a job in today's job
13
-Both the BIND and NSD name servers were developed by having the programmers
14
-paid to work on the programs. PowerDNS was originally commercial software
15
-with the author only reluctantly made GPL after seeing that the market
16
+The only thing that will convince me to implement a given feature for
17
+MaraDNS is cold, hard cash. If you want me to keep a given feature
18
+proprietary, you better have lots of cold hard cash. If you're willing
19
+to opensource your feature, less cash should be sufficient.
21
+Keep in mind that both the BIND and NSD name servers were
22
+developed by having the programmers paid to work on the programs.
23
+PowerDNS was originally commercial software with the author only
24
+reluctantly made GPL after seeing that the market
25
for a commercial DNS server is very small. All of the other DNS servers
26
which have been developed as hobbyist projects (Posadis, Pdnsd, and djbdns)
27
are no longer being actively worked on by the primary developer.
29
-If I were to work on MaraDNS again, it will be a complete rewrite in C++;
30
-if I can get C++ on my resume, I may be able to get a job more easily.
31
+I plan on someday adding standards-compliant BIND zone file support.
32
+After that, I may even add real DNS slave support.
34
-Like anything else, this is not absolute. For example, if I see a large
36
MaraDNS community and a strong demand for new features from that community,
37
-I will change my mind. Should ipv6 start to become dominant, I will update
38
+I will consider their wishes. Especially if some of the members of
40
+have large bank accounts. Should ipv6 start to become dominant, I will update
41
MaraDNS to have full ipv6 support. Should some other technology come along
42
that will require an update to MaraDNS for MaraDNS to continue to function
43
-as a DNS server, I may update MaraDNS to use that technology.
44
+as a DNS server, I may very well update MaraDNS to use that technology.
49
diff -ur maradns-1.2.12.02.orig/doc/en/source/maradns.ej maradns-1.2.12.02/doc/en/source/maradns.ej
50
--- maradns-1.2.12.02.orig/doc/en/source/maradns.ej 2005-12-21 01:30:34.000000000 -0600
51
+++ maradns-1.2.12.02/doc/en/source/maradns.ej 2006-08-10 00:21:42.000000000 -0500
53
(as opposed to DOS or UNIX newlines), while the file will parse, any errors
54
in the file will be reported as being on line 1.
56
-The maximum allowed number of threads is 125; this is a hard limit because
57
-there may be problems with some pthreads implementations causing MaraDNS to
58
-hang if this number is higher.
59
+The maximum allowed number of threads is 5000.
61
The system startup script included with MaraDNS assumes that the only
62
MaraDNS processes running are started by the script; it stops <i>all</i>
64
MaraDNS does not use the zone file ("master file") format specified in
67
-If a wildcard MX record exists in the form "*.example.com", and
68
+MaraDNS default behavior with star records is not RFC-compliant.
70
+if a wildcard MX record exists in the form "*.example.com", and
71
there is an A record for "www.example.com", but no MX record for
72
"www.example.com", the correct behavior (based on RFC1034
73
<hibit alt="section ">§</hibit>4.3.3)
74
is to return "no host" (nothing in the answer section, SOA in the
75
authority section, 0 result code) for a MX request to "www.example.com".
76
Instead, MaraDNS returns the MX record attached to "*.example.com".
77
+This can be changed by setting <tt>bind_star_handling</tt> to 1.
79
Star records (what RFC1034 calls "wildcards") can not be attached to
82
MaraDNS, like every other known DNS implementation, only supports a
85
-MaraDNS does not send more than one DNS packet to a given DNS server when
86
-processing a DNS request; this is not a serious problem because most
87
-client implementations send multiple DNS packets to a recurisve DNS server
88
-when processing a DNS request.
90
MaraDNS spawns a new thread for every single recursive DNS request
91
when the data in question is not in MaraDNS' cache; this
92
makes MaraDNS an excellent stress tester for pthread implementations.
94
<i>These are features which will not be implemented in the 1.2 release
97
-MaraDNS does not have a "fully qualified host name" record, which would
98
-automagically create a PTR record from an A record.
100
MaraDNS does not have a disk-based caching scheme for authoritative
105
MaraDNS only has limited authoritative-only support for IPv6.
107
-MaraDNS generally does not support any DNS features which are not present
108
-in RFC1034 and RFC1035. The exceptions are the ability to decompress some
109
-RRs not in RFC1035, and zone file support for AAAA records (RFC 1886) and
110
-SRV records (RFC 2052).
112
MaraDNS only allows wildcards
113
at the beginning or end of a host name. E.g. names with wildcards like
114
"foo.*.example.com". "www.*" will work, however, if a default zonefile is