More DNS Trouble

[sky-knight]

Cox name servers: 68.105.28.16, 68.105.29.16, 68.105.29.16, and 68.105.29.17

These are currently failing SORBS, SpamHaus, and intermittently URIBL

Untangle's DNS is failing URIBL.

So now I'm down to my own VPS based resolver.

[fasttech]

I just skimmed the logs on a v11 that's on those dns servers, is that why this email, for example, is scored a 15 but the detail for URIBL is 0?

URIBL_BLOCKED[0.0] URIBL_JP_SURBL[1.2] BAYES_99[3.5] RCVD_IN_BL_SPAMCOP_NET[1.3] SPF_PASS[-0.0] BAYES_999[0.2] HTML_MESSAGE[0.0] MIME_HTML_ONLY[0.7] SPAMBLOCKER_FLAGGED[8.0] UNPARSEABLE_RELAY[0.0] T_REMOTE_IMAGE[0.0]

[dmorris]

URIBL_BLOCKED means the uribl lookup was blocked, not that that mail should be blocked.

[fasttech]

Hmmmm... I just pulled 10,000 events in the log and just skimming it looks like every URIBL is zero.

[fasttech]

Yeah, I get that now, I see every lookup for that in the log is blocked.
Spam is still effectively filtered, just not using that list I guess.

It's too bad that column isn't in the reports.

[fasttech]

I have a couple of local bind dns servers already on that network, would just need to copy the static dns out of the Untangle install over and ipconfig /flushdns or reboot everything...

... is it worth the trouble though?

[sky-knight]

I'm rather rapidly moving to the conclusion that Untangle should have a local Bind cache of its own available... this is getting annoying.