25
25
<li><A href="#1.2.03">Updating from 1.2.03 to a later 1.2 release</A>
26
26
<li><A href="#1.2.12">Updating from 1.2.12 to a 1.3 release</A>
27
27
<li><A href="#1.3">Updating from 1.3 to a 1.4 release</A>
28
<li><A href="#2.0">Updatring from MaraDNS 1.4 to MaraDNS 2.0</A>
31
30
This document is divided in to two parts; anyone upgrading from a
364
363
name "*.example.com." (with a literal star in the domain name), which is
365
364
usually not what one wants.
368
<h1>Updatring from MaraDNS 1.4 to MaraDNS 2.0</h1>
370
MaraDNS 2.0 is MaraDNS 1.4 with all recursive support removed from the
371
maradns daemon and done with the separate daemon <tt>Deadwood</tt>.
376
<li>MaraDNS can no longer serve both authoritative and recursive records on
379
<li>While Deadwood uses a compatible rc file format, there are enough
380
differences between a mararc file (MaraDNS' configuration file) and
381
a dwood3rc file (Deadwood's configuration file) that a conversion
382
has to be done by hand.
386
The most important thing to keep in mind when converting a mararc file to
387
a dwood3rc file is that Deadwood does not support the following mararc
395
<li>bind_star_handling
396
<li>csv2_default_zonefile
397
<li>csv2_synthip_list
398
<li>csv2_tilde_handling
400
<li>default_rrany_set
401
<li>dos_protection_level
404
<li>ipv6_bind_address (bind_address supports one or more ipv6 addresses if
405
Deadwood is compiled with IPv6 support)
412
<li>notthere_ip (If you want to make money with NX redirects, let's talk money)
413
<li>recurse_delegation
414
<li>reject_ptr (but Deadwood does support reject_aaaa)
416
<li>retry_cycles (use num_retries instead)
421
<li>tcp_convert_server
422
<li>timestamp_type (We assume the logger makes a timestamp for us)
423
<li>verbose_query (verbose_level will do this at a level of 100 or more)
424
<li>zone_transfer_acl
427
Also, Deadwood handles "verbose_level" differently; to get fully verbose
428
messages, "verbose_level" has to be 200 (as opposed to MaraDNS' 10).