Re: NULLS

Hi Brad, I believe you are correct as well.  After reading this:
http://bind-dlz.sourceforge.net/mysql_driver.html

It seems the NULL's are very important.  This section of the docs was  
particularly explanative:
      The data string is "built" by concatenating fields 4 through 12
      together, with a space added in between each. Fortunately, the
      number of spaces in between doesn't matter, as long as there is
      at least one. This makes it easy for one query to return a
      number of different DNS types. If a field returned by the
      allnodes query is NULL, nothing is appended by that field. The
      driver then appends a space to the end of the string and
      continues to the next field. This is done until fields 4
      through 12 (or however many fields you have in the query) are
      processed.

So, in my case, since there were 'NULL' and 0 on the fields, those  
were getting appended, and of course, neither of those are valid in a  
DNS result.

Thanks.

On May 8, 2009, at 9:13 PM, Bradley Giesbrecht wrote:

> After doing some quick testing I think this is because of the way dlz
> builds the reply from the result of the query.
>
> I'd guess the value of mx_priority is your problem.
>
> You could add a "case" statement to your query to return null if the
> dns query type doesn't need mx_priority.

-- 
Scott * If you contact me off list replace talklists@ with scott@ *


------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com