I would _strongly_ recommend against hosting your own DNS, simply because you are a single point of failure. A targeted DDoS attack, an intrusion (there are bots bruteforcing all the time!) or even just an outage could fuck everything up royally (including mail deliverability!). Instead try hosting your DNS with a company which specialises in reliable DNS, such as HE.net or Cloudflare.
Yeah, uh, I kinda know all this. It's my job. Regardless, I'm not worried in the slightest. I have hardware mitigation in place as well as a dynamic iptables daemon that sniffs out attacks fairly nicely. I also challenge a bot to bruteforce anything I have, especially since I have root logins disabled, and I use a two step authentication scheme for SSH. I don't run any sort of vulnerable web applications and the majority of my site is password protected with randomly generated passwords. Also, please never recommend the garbage that is Cloudflare to anyone. Anyone with any sort of knowledge of netcat can sniff out the true IP of a server behind it. A mail server can also give this away, so it's much better to use an external server for that. CF also gives a bad reputation to any site that uses it since malware oriented forums, torrent indexes, and DDoS for hire services tend to use it to try and hide, and the company is known for letting these things slide despite their ToS.
The registrar has nothing to do with the DNS propagation unless they host the resolve servers as well. Not to mention it's been well over 72 hours.
@
x65943:
@
x65943:
@
JuanMena:
