ok so im setting up DNS for a side project and keep going back and forth on running my own nameservers lol some ppl say its the obvious best practice, others say it adds complexity for no real gain. ive had one bad experience in the past where a host held my DNS hostage during a migration, so Im a bit paranoid now. what do you do, and why? interested in what went wrong for you as much as what went right. seriously need help here 馃槶
Why Do Seasoned Admins Insist On Running My Own Nameservers???
Accepted solution
Jump to the replywhatever u choose, keep TTLs reasonable and lower them a day before any migration. most DNS horror stories i've seen came from long TTLs and forgotten records, not from teh provider itself.
The Apex Domain Mystery: Without Www It Throws A Certificate Warning
Related topics
- before i commit to splitting registrar and dns provider... talk me out of it
- lessons from using the hosts nameservers with a small business site. agree or disagree?
- Am I Crazy For Considering Using The Host's Nameservers On A Side Project?
- Before I Commit To Running My Own Nameservers... Talk Me Out Of It
- LESSONS FROM KEEPING DNS AT THE REGISTRAR WITH A PERSONAL BLOG. AGREE OR DISAGREE?? 馃槶
- The Clients .io Domain Vanished From The Internet After Turning On DNSSEC. Did I Break It?
Reply to this topic
Sign in or create an account to reply.