- Joined
- Oct 12, 2015
- Messages
- 1,753
- Trophies
- 0
- Location
- kys
- Website
- camilla.hostfree.pw
- XP
- 1,437
- Country
ive registered http://azura.ga , but it wont pinpoint to my domain's dns. its registered and all in my cpanel but it still doesnt work. help ?
ill give it until saturdayI think you need to wait a bit longer. I registered a new domain recently and it took much longer than that for the DNS data to propagate.
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.If you've not done so yet, configure your router to use Google's DNS servers. Propagation will speed up tremendously. Also, are you self-hosting your DNS server, or is this shared hosting with third party nameservers? Any time I add a domain to my dedi, it's online in a matter of seconds thanks to running my own BIND9 server.
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.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.
It totally shouldn't. 24 hours at most and even that is stretching it.Normally takes around 24-72 hours for this to work.
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.This is a free domain service, it's bound to be slow to work.
Just to say though I'm unreliable for anything tech related.
Being corrected is how you learn.(implying I can read and understand anything to do with computers properly, or even a simple sentence)
(why did I even bother wasting my time here?)