4
4
* Updating from 1.2.03 to a later 1.2 release
5
5
* Updating from 1.2.12 to a 1.3 release
6
6
* Updating from 1.3 to a 1.4 release
7
* Updatring from MaraDNS 1.4 to MaraDNS 2.0
9
8
This document is divided in to two parts; anyone upgrading from
10
9
a 1.0 release to a recent 1.2 release will need to look over
291
290
Have csv2["*.example.com."] will result in a zone file for the
292
291
domain name "*.example.com." (with a literal star in the domain
293
292
name), which is usually not what one wants.
295
Updatring from MaraDNS 1.4 to MaraDNS 2.0
297
MaraDNS 2.0 is MaraDNS 1.4 with all recursive support removed
298
from the maradns daemon and done with the separate daemon
299
Deadwood. Because of this:
301
* MaraDNS can no longer serve both authoritative and recursive
302
records on the same IP.
303
* While Deadwood uses a compatible rc file format, there are
304
enough differences between a mararc file (MaraDNS'
305
configuration file) and a dwood3rc file (Deadwood's
306
configuration file) that a conversion has to be done by
309
The most important thing to keep in mind when converting a
310
mararc file to a dwood3rc file is that Deadwood does not support
311
the following mararc parameters:
318
* csv2_default_zonefile
320
* csv2_tilde_handling
323
* dos_protection_level
326
* ipv6_bind_address (bind_address supports one or more ipv6
327
addresses if Deadwood is compiled with IPv6 support)
334
* notthere_ip (If you want to make money with NX redirects,
337
* reject_ptr (but Deadwood does support reject_aaaa)
339
* retry_cycles (use num_retries instead)
345
* timestamp_type (We assume the logger makes a timestamp for
347
* verbose_query (verbose_level will do this at a level of 100
351
Also, Deadwood handles "verbose_level" differently; to get fully
352
verbose messages, "verbose_level" has to be 200 (as opposed to