Applications (especially CNode) can now make significant use of DNS servers.

To avoid overloading other servers (not necessarily your ISP) you can use our DNS servers:

ns1.cybercomplex.net
Location: Germany/Frankfurt
IPv4: 51.75.75.243
IPv6: 2001:41d0:701:1100::452

ns2.cybercomplex.net
Location: Canada/Beauharnois
IPv4: 142.4.202.62
IPv6: 2607:5300:101:0:0:0:0:75d

ns3.cybercomplex.net
Location: Poland/Warsaw
IPv4: 80.211.250.127
IPv6: fe80::250:56ff:fea9:8da0

ns4.cybercomplex.net
Location: Australia/Sydney
IPv4: 139.99.170.90
IPv6: 2402:1f00:8100:400::125a

You can also set up your own DNS server (or just DNS cache) on your LAN.
This is especially important if you have several/many BOINC clients and CNode app.
You can check which of the above DNS will be the best (geolocation).

My ISP Charter Spectrum has a poor performing DNS server so I long ago switched to using Google's 8.8.8.8 and 8.8.4.4.
I'd like to understand why use a different more distant DNS server.

The biggest problem from my perspective is that ISPs throttle the upload speed to a fifth of the download speed just so they can charge more if they can get you to buy a faster service.

---

I run Unbound as a recursive resolver on my home network, so I am querying the root and authoritative servers directly. Works great.

---