Re: [MaraDNS list] read slashcommand causes Host name must be at beginning of a line

> I have plans today so I will not be able to continue looking at the
> bug right now, but I hope to have time in the next day or two to look
> at it.

I was able to make some time to fix this bug.  Karim, when you get a
change, please download and compile the following tarball to verify
that it resolves your issue:

http://maradns.org/download/2.0/snap/maradns-Q.20111009.1.tar.bz2

(This is a 2.0 release, so recursion is provided by Deadwood; if you
just want the patch that fixes the issue, explode the tarball and look
in the maradns-Q-20111009.1/update/2.0.04 directory)

My current plan for MaraDNS is as follows:

* I plan on releasing Deadwood 3.0.04 in early November.  This is only
three months after the 3.0.03 release, but I would like to update the
version of Deadwood for my next MaraDNS release.

* I plan on releasing MaraDNS 2.0.04 and 1.4.07 in early December.

To release 1.4.07, I would like to backport the following 2.0 bug
fixes in to the 1.4 branch.  These patches can be found in the
maradns-Q-20111009.1/update directoru for the tarball of today's
MaraDNS snapshot:

* maradns-2.0.01-fetchzone.patch: typo fix

* maradns-2.0.02-axfr_over_udp.patch: Fixes AXFR-over-UDP issues

* maradns-2.0.02-rfc2317.patch: Allow RFC2317-compliant hostnames (with /)

* maradns-2.0.02-debian_bug_607739_fix.patch: Show hostname when
complaining about DDIP name

* maradns-2.0.03-angeld.patch: Fix issue with zone transfers when
there are a lot of FQDN records

* maradns-2.0.03-karim_bug.patch: Fix issue with '/read' directive

(It is non-trivial to backport the "big_any" fix from 2.0 to 1.4, so
people who want MaraDNS with this bug fixed will have to use MaraDNS
2)

- Sam