(Quote)

important they could be for your applications, DNS, firewall rules, allowlists, and other configurations. However, at this stage, completing the restoration as quickly as possible has become the prio

(Quote)

I'm not asking people to spend million on duplicate VMs - don't get me wrong - it depends on your own downtime risk tolerance, ability to respond fastly and fix it, and TTL of your own DNS entries and

(Quote)

(Quote)

(Quote)

There's no such thing as host-provided backups. Proper people who want real redundancy and backups run systems with low DNS ttl + full-clone backup systems known as "hot spares" read

yeah that's something that i'd have to do. i was panicking because it takes tremendous work to do that change the DNS and make sure the new VPS is okay though I am using podman so that makes it easier

Be your own sole Email/Authoritative DNS provider, and then go on from there, like offer hosting/services to friends/family/community.

Custom Reverse DNS

Thanks! Looking promising on the IPv4 side now, need to wait until the new IPv4 addresses have fully propagated through DNS for complete assessment.

Version 3.1.6 is a major update focused on System DNS, Kubernetes operations, load balancing and database backup reliability.

I'll post a YABS from both when I get this other one installed and happy with DNS propagation and stuff. I have a tangentially-related ticket I'm going to open.

DNS, Email

ms 0.0 ms 0% ━━━━━━━━━━━━━━━╌ Google DNS (anycast) ... Google DNS (anycast) 17.7 ms 0.0 ms 0% ━━━━━━━━━━━━━━╌╌ Quad9 (anycast) ... Quad9 (anycast) 180.2 ms

ms 0.2 ms 0% ━━━━━━━━━━━━━━━╌ Google DNS (anycast) ... Google DNS (anycast) 17.6 ms 0.0 ms 0% ━━━━━━━━━━━━━━╌╌ Quad9 (anycast) ... Quad9 (anycast) 180.2 ms

The one thing that changes on your side is the IP address of your service. Please remember to update any DNS records, firewall rules or allow lists that reference the current IP once your migration is

(Quote)

(Quote)