So I wasn't crazy in connecting a trail of other issues to it, the popular DNS resolvers were overloaded. Honestly I didn't suspect that, I forget just how many devices are pinging Facebook constantly

I am hesitating a bit if should upgrade to one much better server or mirror the content to another cheap server and have 2 mediocre servers serving files to users with some round-robin DNS.

(Quote)

(Quote)

On Twitter you can even find reports, that dns resolvers got killed because FB died.

(Quote)

Routing issues resulting in the DNS servers being unreachable (both IPv4 and IPv6)

Seem DNS issues.

At first, we were using two small dedis from online.net with round-robin DNS and mirroring the content on both servers, but the approach was not so easy to use and we gave up on it when cloudflare kic

* Networking IPv4, IPv6, TCP/IP, LAN/WAN, DHCP, DNS

(Quote)

(Quote)

Thanks for sharing, it's indeed a problem especially for the SMTP server and DNS server use case.

* DNS server (UDP port cannot change)

Graphed DNS lookup times over 24 hours from various locations to VirMach Phoenix.

(Quote)

So for some sites I'll be using cloudflare storage, but not dns, or for some, dns and storage, but not domain.

* DNS and access to private queryes? Yes

It is worked now.. check this thread: https://talk.lowendspirit.com/discussion/3402/adguard-home-dns-over-tls-issue#latest

If you're running a DNS over TLS server and using Let's Encrypt, it will break on Android. I tried adding the CA manually, no cigar. On android, Private DNS using Let's Encrypt will not work.