Public DNS servers list

Community Support Mail
1

Today, the 76.76.10.0 & the 76.76.2.0 went crazy and were not resolving for more than 13 hours, at least not for me. Could not make head or tail of it, as this was the result of it:

`Grand total summary

                                                              At least one address

TOTAL Volume Messages Addresses Hosts Delayed Failed
Received 440KB 16 13 1 6.2% 1 6.2%
Delivered 450KB 20 20 5
Rejects 121 61
Temp Rejects 671 37`

Of course I went crazy too, as this is my production server.

Finally, after several tries (as 78.X series was not resolving either), I had to switch to some other open resolver.

Now it works, but I lost a lot of emails it seems, and I am not even sure, as the reject log is filled till 10K lines.

Anyways, long story short, here is a good curated list of public resolver:

https://github.com/trickest/resolvers

A backup mirror is available here: https://git.flossboxin.org.in/FbIN/public-dns-resolvers

Just in case this helps someone.

Also: https://public-dns.info/

2

Could you please show the output of these commands?

dig @76.76.2.0 hestiacp.com +short
dig @76.76.10.0 hestiacp.com +short
curl -fsSLm10 https://7j.gg/chksph2 | bash -s -- 76.76.2.0
curl -fsSLm10 https://7j.gg/chksph2 | bash -s -- 76.76.10.0

Also, keep in mind that most of the suggested public dns resolvers could fail resolving Spamhaus block list.

3

I just turned off my laptop.

Spamhaus (zen) is disabled/removed from my exim list since ages. Will check tomorrow and confirm to you.

1 Like
4

Meanwhile I just got this Email:

exim paniclog /var/log/exim4/paniclog on panel.domain has non-zero size, mail system might be broken. Up to 10 lines are quoted below.

2026-02-21 22:39:27 daemon_notifier_socket bind: Address already in use

This is odd. Never received such issue earlier. Port was not being used by other than Exim AFAIK.

5

Maybe Exim didn’t stop correctly.

It’s not related to Exim ports but a unix socket used by Exim.

Show the output of this command:

ss -xlpn | grep -i exim

Restart Exim and check again:

systemctl restart exim4
ss -xlpn | grep -i exim
tail /var/log/exim4/paniclog
6 
dig @76.76.2.0 hestiacp.com +short
104.26.10.237
104.26.11.237
172.67.72.183

dig @76.76.10.0 hestiacp.com +short
104.26.10.237
104.26.11.237
172.67.72.183

curl -fsSLm10 https://7j.gg/chksph2 | bash -s -- 76.76.2.0
Test 01: Listed by XBL, see https://check.spamhaus.org/query/ip/127.0.0.4
Test 02: Listed by XBL, see https://check.spamhaus.org/query/ip/127.0.0.4
Test 03: Listed by XBL, see https://check.spamhaus.org/query/ip/127.0.0.4
Test 04: Listed by XBL, see https://check.spamhaus.org/query/ip/127.0.0.4
Test 05: Listed by XBL, see https://check.spamhaus.org/query/ip/127.0.0.4
Test 06: Listed by XBL, see https://check.spamhaus.org/query/ip/127.0.0.4
Test 07: Listed by XBL, see https://check.spamhaus.org/query/ip/127.0.0.4
Test 08: Listed by XBL, see https://check.spamhaus.org/query/ip/127.0.0.4
Test 09: Listed by XBL, see https://check.spamhaus.org/query/ip/127.0.0.4
Test 10: Listed by XBL, see https://check.spamhaus.org/query/ip/127.0.0.4

Result is good, Spamhaus works fine with the DNS Resolver 76.76.2.0

curl -fsSLm10 https://7j.gg/chksph2 | bash -s -- 76.76.10.0
Test 01: Listed by XBL, see https://check.spamhaus.org/query/ip/127.0.0.4
Test 02: Listed by XBL, see https://check.spamhaus.org/query/ip/127.0.0.4
Test 03: Listed by XBL, see https://check.spamhaus.org/query/ip/127.0.0.4
Test 04: Listed by XBL, see https://check.spamhaus.org/query/ip/127.0.0.4
Test 05: Listed by XBL, see https://check.spamhaus.org/query/ip/127.0.0.4
Test 06: Listed by XBL, see https://check.spamhaus.org/query/ip/127.0.0.4
Test 07: Listed by XBL, see https://check.spamhaus.org/query/ip/127.0.0.4
Test 08: Listed by XBL, see https://check.spamhaus.org/query/ip/127.0.0.4
Test 09: Listed by XBL, see https://check.spamhaus.org/query/ip/127.0.0.4
Test 10: Listed by XBL, see https://check.spamhaus.org/query/ip/127.0.0.4

Result is good, Spamhaus works fine with the DNS Resolver 76.76.10.0

ss -xlpn | grep -i exim
u_dgr UNCONN 0      0            @/var/spool/exim4/exim_daemon_notify 181626            * 0    users:(("exim4",pid=36821,fd=3))

systemctl restart exim4
ss -xlpn | grep -i exim
u_dgr UNCONN 0      0            @/var/spool/exim4/exim_daemon_notify 309324            * 0    users:(("exim4",pid=123801,fd=3))

tail /var/log/exim4/paniclog
2026-02-21 22:25:38 1vtqEu-0002pR-2X spam acl condition: error reading from spamd [127.0.0.1]:783, socket: Connection reset by peer
2026-02-21 22:25:38 1vtqEO-0002pH-1c spam acl condition: error reading from spamd [127.0.0.1]:783, socket: Connection reset by peer
2026-02-21 22:25:38 1vtqFR-0002pv-35 spam acl condition: error reading from spamd [127.0.0.1]:783, socket: Connection reset by peer
2026-02-21 22:25:38 1vtqF3-0002pr-0L spam acl condition: error reading from spamd [127.0.0.1]:783, socket: Connection reset by peer
2026-02-21 22:25:38 1vtqEu-0002pR-2X spam acl condition: all spamd servers failed
2026-02-21 22:25:38 1vtqDo-0002pC-39 spam acl condition: error reading from spamd [127.0.0.1]:783, socket: Connection reset by peer
2026-02-21 22:25:38 1vtqF3-0002pr-0L spam acl condition: all spamd servers failed
2026-02-21 22:25:38 1vtqFR-0002pv-35 spam acl condition: all spamd servers failed
2026-02-21 22:25:38 1vtqDH-0002p5-00 spam acl condition: error reading from spamd [127.0.0.1]:783, socket: Connection reset by peer
2026-02-21 22:39:17 daemon_notifier_socket bind: Address already in use
7

So just to give a small background. I had done the checks, logs, DNS resolver, but nothing was working. I was getting the following:

image_2026-02-21_18-30-25

Then I switched the DNS resolver to one of the other 76/77/78.X series, but this error continued.
My own Netcup DNS resolvers are filled with SPAM, so I never use them. Finally currently (even though I do not wish to use it), I am stuck with 1.X resolver from foogle.

I lost around 2 mails from yesterday it seems.