How I learned to stop worrying and replaced GratisDNS
This might be helpful - not just for those of you moving from gratisdns, but for anyone looking for a DNS hosting provider.
While I subconsciously knew this would happen when one.com bought GratisDNS, I'm ashamed to admit that I did not plan accordingly. The other day all current users of GratisDNS got the troubling email from the new owners that they'd migrate all zones from the multiple GratisDNS servers to 2 one.com servers "march 2022" so likely in a month.
With no further information tangible information on the migration specifics or future cost, this triggered me to look for other providers of DNS hosting.
My requirements were (are):
[R1] DNSSEC: This is a must!
[R2] Decentralized. There's way too much centralization, perverting DNS.
[R3] Hidden Master: Very nice to have, however can live without.
[R4] API: If hidden primary isn't supported, this is high on the list.
R5. Cheap or free: I need to pay for food and coffee.
Started investigating some possibilities (In alphabetical order):
CloudFlare.
Hetzner.de (.com).
QuickDNS.dk.
Simply.com
Migration Process
- Select a less critical domain for testing.Luckily I have quite a few domains.
- Disable DNSSEC.
- Create zone on selected provider.
- Transfer, add and verify all RR's
- Test with dig to ensure RR's are correct (use @ns.provider.tld with dig and e.g. OpenDNS or even 1.1)
- (Re)enable DNSSEC.
- Test with dig that DNSSEC works. dnsviz.net is awesome for this too, especially when you're tired and can't read dig output :)
- Test DKIM some more. Fatfingered during testing.
This is (opinionated) how they fared during my testing.
No comments:
Post a Comment