Re: some problems with bopm doing blacklist lookups
Deedra Waters <[email protected]>
| Newsgroups | gmane.network.irc.bopm |
|---|---|
| Message-ID | <Pine.LNX.4.58.0311140540140.29702@simba> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The main point where it seems to happen is durring netsplits. As for the operserv part of what I pasted, md had to kill it because it was doing those errors with a netsplit of a good 1600 users. I don't think it's the resolvers where bopm is sitting, though I could be wrong of course. On Fri, 14 Nov 2003, Andy Smith wrote: > 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... > > - -- Freenode staff member: [email protected] , http://www.freenode.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/tMKnU5AGPOTGNc8RAsfbAJ4msIygPdGoTVPJjs3b3gj6goyQ1QCfR/SW EXiTMuFcoLc/S46Stdy4wh8= =o3kl -----END PGP SIGNATURE-----