Re: some problems with bopm doing blacklist lookups
Andy Smith <[email protected]>
| Newsgroups | gmane.network.irc.bopm |
|---|---|
| Message-ID | <[email protected]> |
On Thu, Nov 13, 2003 at 01:39:28PM -0600, Deedra Waters wrote: > 12:22 < ~proxyscan:#freenode-status> DNSBL -> Lookup error on > 144.161.136.144.opm.blitzed.org: Server failure > 12:22 < ~proxyscan:#freenode-status> DNSBL -> Lookup error on > 158.133.217.12.opm.blitzed.org: Server failure > 12:22 < ~proxyscan:#freenode-status> DNSBL -> Lookup error on > 176.159.214.212.opm.blitzed.org: Server failure I'm not sure whether this is reporting a failure with the authoritatice servers for opm.blitzed.org, or whether it comes from your own resolver. I can't reproduce it right now on the auth. servers for opm.blitzed.org but it could have been a momentary glitch. If you have your own nameservers you wish to use we could set up for you to get an XFR of this zone. > 12:22 *** Quits: proxyscan [[email protected]] (Killed by > OperServ ()) No idea about this bit. Failing to look things up should never cause the BOPM code to crash... -- Andy Smith -- Occasional BOPM Developer And Support Monkey. Please copy all BOPM support queries to the BOPM list, _not_ just directly to me! If I've helped you with BOPM then please check my wishlist! http://www.amazon.co.uk/exec/obidos/registry/23IJ4U7N4J3X9
signature.asc
(application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE/tIXQIJm2TL8VSQsRAr+1AJwPgi8PYREd2DF/aOuSg7x7NFjzBwCeKW8z gzHHULZILjCqvSYfEnWX8yo= =36Rz -----END PGP SIGNATURE-----