Re: BIND-DLZ cache corruption issue.
Graeme Fowler <[email protected]> Fri, 01 Oct 2010 09:45:18 +0100
| Newsgroups | gmane.network.dns.bind9.dlz |
|---|---|
| Message-ID | <1285922718.18402.3.camel@localhost> |
On Thu, 2010-09-30 at 20:46 -0700, Michael J. Ayers wrote: > This particular issue is cannot be replicated with a flat text zone > file. That issue was fixed with I believe the 9.5 release. BIND now > properly throws an error when it encounters a TXT record that is > longer than 255 bytes in length or is not properly closed in > quotations. So... Set the database schema such that TXT records have a maximum length of 253 - char(253) in SQL parlance - and then ensure that the query BIND makes through the DLZ driver has escaped quotes at either end. That assumes that the quotes are included in the character string length as defined in the RFC for TXT records (1034 or 1035 IIRC). That way you eliminate the possibility of corrupt data as described. It may still be possible to malform the data, but not in the way you describe. Graeme ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev