trying tor respond to help for NAPTR entries

[Sam Trenholme]

> Error: Invalid character between chunks; this might be
> caused by a TXT RR not terminated by a ~ character Error is on line 12 in file
> myzone.zone context of error: ';'myservice';'a' e (closing this file)

Thank you for noticing this; this is indeed a bug in the MaraDNS csv2
parser.  Let me just post some of the blog entry I just posted:

You know, it’s always a little embarrassing for me to have a bug in my
code. A part of me wishes I was perfect and did not make mistakes, and
has the notion it reflects poorly on me if a piece of code has a bug
in it — even though it plain simply is not humanly possible to make a
program as complex as a DNS server without any bugs.[1]

There was a bug in the code that parses NAPTR records that makes it
impossible to parse NAPTR records unless the ~ is *not* used to
separate records. The workaround is to not use the ~ to separate
records in zone files with NAPTR records; the fix is available here
(as well as attached to this email):

http://www.maradns.org/download/patches/maradns-1.4.03-naptr_parsebug.patch
http://www.maradns.org/download/1.4/snap/2010/maradns-Q.20100512.1.tar.bz2

[I also did an IPv6 change; RTFB at http://maradns.blogspot.com/ ]

- Sam

[1] If you’re an ignorant DJB fanboy who still thinks DjbDNS is
perfectly secure and has no bugs, you’re wrong.

Note: I do not answer MaraDNS (including Deadwood) support requests
sent by private email without being compensated for my time. A MaraDNS
support request is any and all discussion you may wish to have about
MaraDNS in private email; if you want to email me to talk about
MaraDNS then, yes, that is a support request. I will discuss rates if
you want this kind of support. Thank you for your understanding.

MaraDNS security vulnerability reports, however, will be dealt with
without charge and kept confidential. If you don't know what Bugtraq
is, then, no, your email is not a security report. It is not a
security report unless you've done due diligence to determine how the
security bug you think you found can reasonably be exploited.