I used to have a local setup where depending on which user an application ran under traffic would go through different VPNs (including different DNS servers even though this is set system wide by reso

I'd argue that both nameservers should send both A records. In most DNS servers, the order is randomised on replies, and client will typically connect to the first and then the second.

Definitely low TTL in this case. This type of DNS failover works very well in practice.

(Quote)

If an attacker already compromised something like an NTP daemon or recursive DNS resolver enough to execute code and interact with kernel functionality, then you already have a serious security proble

is compromised, say an NTP daemon or a recursive DNS resolver, it could trigger module loading and then exploit the system. In essence, even if the modules are not loaded, every single process on the

A solution I use myself (because I selfhost my DNS) is that with PowerDNS (and maybe others) you can create a LUA record that checks regularly if port 80 or 443 is responding; if not, it doesn't retur

I would like to thank you all, for your help and suggestions. For the moment, we will try the DNS Fail-Over method, with GCore, as someone mentioned. It seems to be the easiest method for now, so we w

(Quote)

At that point, either machine can be used to access the service. If they're near each other geographically, I'd just list both machines in the DNS as round-robin for automatic failover, but failing th

🌐 Update: Dynamic DNS support is live!

my 9950x in SLC with @fiberstate is giving DNS errors and i can see same errors on their website too while trying to login . Their contact form cannot be submitted either because of this issue and th

I can enter in the machine but i cant navigate. browser firing me DNS_PROBE_STARTED. Its like its not solving dns

(Quote)

yeah my .de sites were down. their entire DNS failed.

* If you're having DNS issues, would you know how to use tcpdump and dig to troubleshoot?

The fact that the name was previously held was known. Correct?

Just DNS hosting.

For registration or for DNS hosting?

Then, use small vps from e.g Gullo's @Cam , Tierhive @backtogeek, @Nube, @AliceNetworks to maintain the dns (or cloudflare) and do DR (provision new temporary server, set it up, synced it) in case one