ns_initparse() returning errors

[Christopher Ambler]

Okay, seeing that this is the right place, here's my question -

When making queries to verify an SOA for a zone, I am seeing
errors come back when checking particular name servers.

Specifically, ns_initparse() returns the error "Message too long"
after the call to res_mkquery() and then res_send(). A response
is received, but then ns_initparse() chokes on it.

Can anyone shed some light on this? The length of the message
in the response buffer is well under other, valid, responses that
I've received.

I'm making these calls in a loop, and I've found that after
receiving this error, the state of the _res structure is unstable,
forcing me to call res_init() before proceeding with more.

Also, while I'm here, does anyone know if these resolver
libraries are thread-safe? That is, I note that they make
use of a shared buffer (in _res). Does that mean that
forking off multiple parallel queries is a bad thing?

Believe it or not, this is the first time I've delved into
these routines, so some adult supervision is appreciated.
This will teach me to say, "No, let me do it, I really should
know this library. It'll be a quick learning experience" :-)

Thanks much in advance.

--
Christopher Ambler
CTO, Image Online Design, Inc.
The .Web Internet Domain Registry
chris at the.web