However, I want to setup a DNS failover in the case that my Ramnode server becomes unavailable, and therefore would prefer to go with a different provider in a different datacenter.

Or if you don't want to rely on DNS round robin, passthrough from one nginx, to some "filtering" nginxes, passing through your app?

They're perfect as DNS.

You now have 10 IPs of OVH Australia, I'm kinda jealous I hope once they deliver my server I can order and remove IPs as well as set reverse DNS and control firewall/DDoS VAC like I can in the FR and

I run my DNS servers off of them - no issues. I'd happily buy from HostUs again.

(Quote)

I'm looking at cloudron.io at the moment. The Cloudron platform includes 1-Click app install, automatic backups, updates, DNS setup, SSL provisioning and a secure firewall.

generally it's easy to get the real ip of a domain proxified by CF, unless the domain has been put behind Cloudflare's DNS right after registration (or moved to the current server after DNS delegation

I'm looking for a self-hosted solution that would work like no-ip / dnsexit / other ddns solutions.

I added my own DNS lookup info, and haven't tested AAAA records yet, but it seems to work fine. HostPing and basic port/lookup is on par with NOCOL that I used 20 years ago- but takes about 1% of the

Hmm will look into it. DNS should work

Is is possible to add a DNS loojup for MX? I have add hostname.com MX as the type but it fails

(Quote)

Which part of "ASN is broken", "certificates are usually not even properly parsed", "whoever gets a certificate from whereever for a given server basically

(Quote)

I'm running production on one of thees. But I have DNS failover and two live backup servers at other hosts and really good backup routines. So if the disk goes, 1 minute later my sites is up and runni

@Hybrid that list is probably all the sites that use Cloudflare DNS, but only the sites that used the reverse proxy are (potentially) affected.

OpenSSH ships with the UseDNS option enabled by default, so it tries to check the reverse DNS of a client's IP. No route to the internet = no route to your DNS server = SSHd waits until the DNS query

(Quote)

The hang on initial connect seems possibly due to dns (dns lookups) being enabled in sshd_config and the delay is because of your notwork (sic) :-)