Germany is now UP
Downtime: 14 min
Target: 46.4.165.226:53
Noticed at: 2021-03-03 03:14:33 (UTC+00:00)

US East is still DOWN
Downtime: 5 min
Target: 162.245.221.19:53
Noticed at: 2021-03-22 10:45:40 (UTC+00:00)
Encountered errors:
New York: Timeout (5 sec)
San Francisco: Timeout (5 sec)
Dallas: Timeout (5 sec)
London: Timeout (5 sec)

US East is now UP
Downtime: 27 min
Target: 162.245.221.19:53
Noticed at: 2021-03-22 11:12:43 (UTC+00:00)

US Central is still DOWN
Downtime: 5 min
Target: 107.155.83.188:53
Noticed at: 2021-04-04 18:26:38 (UTC+00:00)
Encountered errors:
New York: Timeout (5 sec)
San Francisco: Timeout (5 sec)
Dallas: Timeout (5 sec)
London: Timeout (5 sec)

US Central is now UP
Downtime: 13 min
Target: 107.155.83.188:53
Noticed at: 2021-04-04 18:39:28 (UTC+00:00)

I'm aware about issues with monitoring not picking up outages. I'll try to look into it this weekend, lots of stuff going on right now (both private and project related, stay tuned). US East should be up again now, apologies for the inconvenience.

Important! The current US East Node is deprecated effective immediately and has been replaced by a new node, graciously provided by VMSpecialist. This is due to Hyper Expert, the hosting provider of the (now) old US East node, closing down their services in New York. As such the IP addresses of the US East node have changed:

Old IPv4: 162.245.221.19
Old IPv6: 2604:7a80:2001:155:0:0:0:0

*NEW* IPv4: 194.124.76.14
*NEW* IPv6: 2a0b:f300:40c:100:1:1:19ab:29dc

DNS over HTTPS (DoH) and DNS over TLS (DoT) hostnames remain unchanged, i.e. us-east.adhole.org

The old node will remain online for the next 6 hours and will be taken offline at July 12, 2021, 11:59 PM EST by Hyper Export. After that, the old IP addresses will no longer respond to DNS queries. I sincerely apologize for the short notice, I was busy moving.

PS. I'm currently working on better monitoring and should have another node up in Russia this week if all goes according to plan. Stay tuned!

US East is still DOWN
Downtime: 5 min
Target: 162.245.221.19:53
Noticed at: 2021-07-13 07:01:41 (UTC+00:00)
Encountered errors:
New York: Timeout (5 sec)
San Francisco: Timeout (5 sec)
Dallas: Timeout (5 sec)
London: Timeout (5 sec)

US East is now UP
Downtime: 24 min
Target: 194.124.76.14:53
Noticed at: 2021-07-13 07:25:37 (UTC+00:00)

Singapore is still DOWN
Downtime: 5 min
Target: 210.16.120.48:53
Noticed at: 2021-07-21 06:02:43 (UTC+00:00)
Encountered errors:
Singapore: Timeout (5 sec)
Sydney: Timeout (5 sec)
Tokyo: Timeout (5 sec)
Mumbai: Timeout (5 sec)

Singapore is now UP
Downtime: 11 min
Target: 210.16.120.48:53
Noticed at: 2021-07-21 06:13:40 (UTC+00:00)

Singapore is still DOWN
Downtime: 5 min
Target: 210.16.120.48:53
Noticed at: 2021-07-21 06:14:36 (UTC+00:00)
Encountered errors:
Singapore: Timeout (5 sec)
Sydney: Timeout (5 sec)
Tokyo: Timeout (5 sec)
Mumbai: Timeout (5 sec)

Singapore is now UP
Downtime: 6 min
Target: 210.16.120.48:53
Noticed at: 2021-07-21 06:20:27 (UTC+00:00)

Germany is still DOWN
Downtime: 5 min
Target: 46.4.165.226:53
Noticed at: 2021-09-30 20:01:43 (UTC+00:00)
Encountered errors:
Amsterdam: Timeout (5 sec)
London: Timeout (5 sec)
Frankfurt: Timeout (5 sec)
Moscow: Timeout (5 sec)

Germany is now UP
Downtime: 6 min
Target: 46.4.165.226:53
Noticed at: 2021-09-30 20:07:43 (UTC+00:00)

I've been made aware that there are currently issues with DoH and DoT on *some* devices. Upon investigation this is due to Let's Encrypt changing their root certificate yesterday: https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/

As explained in the article above, this shouldn't be an issue for modern devices, as most of them should already trust the new root certificate from Let's Encrypt. However, I received multiple reports of new/updated devices that have issues connecting over DoH and DoT.

Luckily we're not alone, many users around the globe are facing this issue on a wide range of devices and applications. I'm actively following this thread on the official Let's Encrypt forums: https://community.letsencrypt.org/t/help-thread-for-dst-root-ca-x3-expiration-september-2021/149190/660

For now I don't have a solution at hand. I will monitor the situation.

US Central is still DOWN
Downtime: 5 min
Target: 107.155.83.188:53
Noticed at: 2021-10-04 16:25:42 (UTC+00:00)
Encountered errors:
New York: Timeout (5 sec)
San Francisco: Timeout (5 sec)
Dallas: Timeout (5 sec)
London: Timeout (5 sec)

Adhole.org is shutting down

After almost 5 years, it’s time to say goodbye; Adhole.org is shutting down. Time wise it has become too much of a burden for me to continue.

What started as a small single-node Pi-hole instance on a public VPS back in 2017, grew out to become a worldwide multi-node adblocking DNS network with thousands of concurrent users around the globe… but that also meant more server load, which meant upgrading servers, more incident (reports) and as such more work. In other words; the project has become a victim of its own success. The current setup is pestered with continuous stability issues along with (recently introduced) certificate issues and repeatedly changing IP addresses. And since no-one likes an unstable DNS, because as all sysadmins know; ‘it’s always DNS’, I decided to pull the plug.

I would like to thank VM Specialist, Nexus Bytes, Misaka and HostUS for sponsoring nodes, my fellow Patrons Stephen S. and Kevin F. for their continued support over the past years, as well as all the fans out there that reached out to me with improvements or in case something was broken. If you’re looking for an alternative ad-blocking DNS resolver, please check out this list on reddit: https://www.reddit.com/r/privacytoolsIO/comments/kbmp5e/dns_servers_for_adblocking/

Since the endpoints have even made it into XDA articles, I will make sure to keep the domain registered and under my control for the next year, to prevent adhole.org from being abused by DNS hijackers/spoofers.

Thanks and stay safe!