https://dns.google/resolve?name=maxkvm.com&type=A

behaviors with BattleNet (Blizzard) and some DNS providers.

We'll see how much longer 8.8.8.8 keeps SERVFAILing us before trying out Google Cloud DNS.

(Quote)

Edit: Looks like a DNSSEC issue.

This is from local unbound. So it would seem that the DNS server is not directing traffic to the closest endpoint.

There could be a variety of reasons why it may have failed for Google DNS. But it is also rather curious that it worked for 9.9.9.9 (without EDNS0 support) but failed for 9.9.9.11 (with EDNS0 support)

Thanks, that's really weird it doesn't answer to Google DNS (Image)

Then, major recursive DNS providers (Google, Cloudflare, OpenDNS, etc) do respect TTL. Ignore the crappy providers.

(Quote)

(Quote)

I have been using gDNSd 2.4 with geodns and auto failover from 8 locations for a few years. It has worked great. According to hetrixtools I show a 99.999% uptime on websites, even though the underli

(Quote)

@MaxKVM I see that you have all your DNS servers on BuyVM's network. This is perhaps not the best, considering resilience. You probably want to consider hosting DNS on multiple different AS.

The point isn't synching but rather DNS propagation delay plus the fact that many provider don't care sh_t about the rules (and your zone config).

Speaking of DNS, I got an idea: I could always rsync two copies of the website in different locations. The secondary server periodically checks the primary. If the primary is down, the secondary modif

I have been using AWS Route53 for geodns, cheap with low volume ($0.70/million geodns requests/month). Gets pricey when adding failover monitoring, $2.75/mo for https monitoring of each host, so your

... or from a backup or deployment server. But keep DNS in mind which can throw a stick into the gears. And of course while you have something in place many (most, I guess) do not.

ClouDNS?

(Quote)