Help with DNSBL configuration on Exim (using BIND9, public resolvers)

Hi everyone,

I’d really appreciate some help. I’m running into issues with the DNSBL blocklists I’m using in Exim.

I suspect the problem is related to the fact that I’m relying on public DNS resolvers.

My /etc/resolv.conf currently looks like this:

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "resolvectl status" to see details about the actual nameservers.

nameserver 1.1.1.1
nameserver 8.8.8.8

I’ve seen several threads recommending Unbound for DNSBL queries, but I already have BIND9 installed.

Has anyone here set this up with BIND9 and could share some guidance or a working example? I’m a bit hesitant to change things and accidentally break my mail flow.

Another (admittedly hacky) idea I had was to use some paid DNS resolvers that aren’t throttled or blocked by the DNSBL providers, but that feels like a band-aid.

Thanks in advance for any advice!

Spamhaus is the only provider that I know of who blocks open resolvers, and you should just go get a feed from them.

1 Like

Try this once :

1 Like

The fourth option worked. But since I’ll be using it for commercial purposes, I’ll have to pay, lol. Thank you very much. And sorry everyone, I hadn’t found this topic, lol

2 Likes

Ahh. In that case suggest using or setting up your own recursive DNS resolver over some other IP. Maybe on a VPS. Spamhaus is one brand I have started to hate soooo much since I started having issues. Took me so much time and stuff to sort it out.

I agree with you, I’ve been through so much hate these days lol. But thank you so much for helping me. For now, my decision is not to use them; I’m only using these at the moment:

bl.spamcop.net
b.barracudacentral.org

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.