My man, from my experience, don't manage a dns server, use cloudflare or something and point an A record to your server with nginx, that's all.

@Saragoldfarb Why not just use DNS round-robin itself, though? I.e. have both nameservers always return both webserver IPs, then, optionally, withdraw the record for one that is down from both (or fro

I suspect this is not too different from DNS round-robin, with its attendant tradeoff of long failover time vs short TTL. I think I also remember some clients (web browsers) were starting to ignore TT

Server A, IP 1.1.1.1, DNS a.mydomain.com

Unfortunately, the traffic, is, err, encrypted and I can’t seem to hijack the DNS. Bastards.

Yes, I admit thats rather bad. Did they say anything to that? If it cant even handle something small like DNS requests (I presume you did not run a mirror of 8.8.8.8) it probably is not overly useful

that depends on type of attacker , if DNS server was targeted and knocked off , the all the domain will not be solved , so make your domain inaccessible

from my personal experience , yes , it will affect speed on solving DNS , I have my site DNS on Cloudflare , which has bad connection to China , my visitor reports they sometimes have error like &

Questions about DNS and DDoS protection

EDIT: setup dns spf like this:

I personally have a few dns servers in Dallas with radi .. no complaints so fa

* Signup for @Francisco's awesome services and forget about MailChannels or configure the DNS settings for your clients to relay from it;

over to another provider that way you can switch dns over and remain online during an outage.

(Quote)

what i really miss is the ability whm-reseller for auto generating dns record to leverage the pain that currently i have, login into my friend dns panel and setup manually with catchall rainloop+cpan

* Free reverse DNS management

What is the practical implications of such a setup? Why is it recommended to keep two separate installs of bind9 (or any DNS service) instead of just setting up restrictions like above?

The welcome email has been fixed, it was indeed sending the link as http instead of https.

I've only seen this occur when the user's domain has too many additional lookups to do. If you add too many includes you'll hit a cap on reasonable DNS lookups required of recipient servers. Users sho

Seen this one? Seems to be related to maxing out the DNS lookups for SPF records.