Why should I care about DNS?
Ultimately nobody will ever visit your website without a DNS lookup succeeding - If you have your DNS handled by multiple name servers, located around the world, then your clients will receive reliable and low-latency replies to their queries.
My registrar providers free DNS already
Many domain-registrars will provide you with their own nameservers, but if your audience is world-wide then your registrar's name-servers will be far away, increasing latency.
As most registrars are not in the DNS-business their nameservers are frequently slow, and can also suffer from outages - if your nameservers are offline you'll have no visitors.
(Sadly domain registrars seem particularly prone to DNS-outages.)
Where are your name-servers?
When you allow us to manage your DNS records your replies will come from highly-available servers, using anycast, located around the world.
Behind the scenes the DNS infrastructure is Amazon's Route53 service, which has never had a global outage.
Who are you designed for?
We're designed for anybody that needs to have reliable, low-latency DNS which is easy to update & manage.
If you value security, reliability, and low-latency then we're the service for you.
Which Git hosts do you support?
You may use any git-host you wish, even a local and private server of your own such as gogs.
We see the changes when you explicitly push them to your dedicated remote hosted with us.
It might be that you wish to use our git-repository exclusively, but if you wish to add it in as a remote, and leave the primary hosting elsewhere (GitHub, BitBucket, etc) that is absolutely fine.
Why are you removing the webhook support?
The main reason to remove the old webhook support is to improve reliability and simplicity.
Having to adapt our receiver to add a new supported host was a real time-sink, and over time several of the webhook events different services pushed to us changed causing frustrating delays.
Working exclusively as a git-remote allows our code to be clean, and allows our users to host their primary repository wherever is convenient for them, which is much better than mandating a choice of only two hosting services.
Your record format is odd, can you help?
We've put together a simple DNS wizard which will let you generate a series of records which should be sufficient for most typical cases, however if that isn't sufficient and you'd like some extra help get in touch, and we'd be happy to convert your existing zonefiles into the correct format.
Our format is based upon the existing TinyDNS structure, which is easy to parse and generate programmatically, and there are numerous conversion utilities out there to ease the process.
Do you have a record validator?
Yes, you can see the results of our record parser here, which will allow you to validate your records.
Is any of your code available under an open-source license?