(Quote)

I am getting it too (haven't been on WHT for ages, so DNS was fresh)

I don't. Cloudflare's free plan for just DNS works fine for me (Image)

do you have something for like 2012R2 DNS Servers like that?

CloudFlare is working on a new tool called Traffic Manager that is going to add support for DNS Failover to their service, once it's released, everyone is going to be able to have a HA website on the

What u are looking for is not Load Balancing but HA/Failover. Your options depend on your existing infrastructure (you get more options like elastic IPs at AWS e.g.). DNS failover (1 Server + hot stan

Use a service with floating IPs, or go with DNS fail over. Rage4 can do that, although they got pretty expensive.

(Quote)

Sorry, we've fixed the DNS record. If it still doesn't work for you, please use http://lg.dal.us.providerservice.com instead.

We utilize a custom control panel that allows full control of your VPS. A new version was just released and it allows you to manage power, view resources, control DNS, maintain a firewall, and more! P

- Reverse DNS

We have made inquires with APC in SG before. It's transit level. So not the kind of mitigation you want if you receive large (no guaruntees), complex (common attack patterns only i.e DNS-Amp) or frequ

I use both DO and Vultr instances as remote desktops when away from the office and have a script to apt-get all the relevant xfce and x2g0 stuff and even register its IP in DNS remotely, so I can log

(Quote)

Maybe DNS caching?

Please make sure to have your server all presetup with a dns address that you will be using for letsencrypt!

SpamAssassin uses extensive network checks like DNSBL and URIBL lookups and the best of these (Spamhaus, URIBL and SURBL) are now not free if you do more than 100,000 queries per day and they won't wo

If they're existing resources, just let them crawl them. You can always ban individual user agents / crawling patterns if they become problematic. If they're non-existent resources, they should be re…

Some people go for the whitelist approach. Normally you'd just want Googlebot, Bing, Yandex, possibly the Archive bot to come grab your stuff. Ban everything else, especially so if they didn't look fo

I've updated the main post, the problem isn't about DNS.