Lookup Error Problems

Hey,

I'm running bopm v3.1.3. Whenever someone connects, I get the
following output in my log channel:

-----------------------------------------------
<%ProxyBot> DNSBL -> Lookup error on 57.0.9.149.dnsbl.dronebl.org:
Server failure
<%ProxyBot> DNSBL -> Lookup error on 57.0.9.149.ircbl.ahbl.org: Server failure
<%ProxyBot> DNSBL -> Lookup error on 57.0.9.149.cbl.abuseat.org: Server failure
<%ProxyBot> DNSBL -> [email protected] appears in BL zone
tor.ahbl.org (Tor exit server)
<%ProxyBot> DNSBL -> Lookup error on 57.0.9.149.rbl.efnetrbl.org: Server failure
-----------------------------------------------
Of course this varies depending on the IP the user is connecting from.
In the example above, I'm connecting via tor.

I DID read the FAQ entry on this problem, however it didn't help. I'm
running a caching BIND9 daemon on the same machine as bopm.
In /etc/resolv.conf I have the entry "nameserver 127.0.0.1"

I can resolve any other IP perfectly fine, however when I do a manual
lookup on, for example 57.0.9.149.dnsbl.dronebl.org, I get a NXDOMAIN
reply.
This is because that IP does not exist in the DroneBL database. But
why is bopm considering it a Server failure? The IP simply does not
exist in that specific blacklist.
If I do a lookup on a IP address which _IS_ in the dronebl.org
blacklist, it returns the proper 127.0.0.x A record reply.

-----------------------------------------------
hostname$ dig @127.0.0.1 57.0.9.149.dnsbl.dronebl.org

; <<>> DiG 9.4.1-P1 <<>> @127.0.0.1 57.0.9.149.dnsbl.dronebl.org
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 43971
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;57.0.9.149.dnsbl.dronebl.org.  IN      A

;; Query time: 252 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Mon Feb 18 21:24:23 2008
;; MSG SIZE  rcvd: 46
-----------------------------------------------

I do NOT have a firedns.conf file. When I run bopm in debugging mode,
it says something about "error 2." I tried resolving
"57.0.9.149.dnsbl.dronebl.org" on an entirely different system, but I
received the same NXDOMAIN error.

If there is any information that would be more helpful, let me know.

Thank you very much for your time,
~Schiz0