Comment on How do people handle authoritative DNS redundancy for their self-hosted workloads?
mschae@discuss.mschae23.de 4 hours agoInteresting, that’s much more sophisticated than my setup (though to be fair, I host my services on a rented VPS instead of home)!
The issue only occurs with my externally-facing DNS, which is needed to, for example, to reach my Lemmy backend instance (lemmy.pootis.network) and the pictrs deployment. But yeah, internal DNS works perfectly for me and it easily survives a node failure.
Could still set up a recursive resolver for external DNS, but I guess that wouldn’t help other people who use a bad resolver. Tricky situation.
Yeah, the issue is that people’s resolvers are wildly different and I guess some of them do not cater to weird and wacky self-hosting setups (most people just use anycast highly-available DNS, usually provided by a registrar or by some other company).
I had a hunch that resolvers break because one of my nodes does not have a public IPv6 address: meaning,
178.44.116.85, acts as NSns1. It has IPv6 connectivity but no external IPv6;91.219.150.30and IPv62a06:dd00:1:4::4189, acts as NSns2.If node4 decides to break, then
ns2becomes unavailable - but since resolvers can see thatns1does not have an IPv4 address, and since everyone knows that IPv6 is better because 6 is greater than 4, then these resolvers would always preferns2, even though it’s clearly down.This could be solved by asking my ISP to set up a static IPv6 prefix for me (they already provide static IPv4), except my ISP does not do that, unfortunately. I could also rent another VPS (so I would have two VPS’es, giving me some resilience from downtimes) but that means extra $$$… anyway, I guess I should probably test the IPv6-preference hypothesis first and then act on the results.