I switched to deSEC because they allow you to create tokens for DNS-01 validation which are tightly scoped to a single subdomain. This means I have a VM running "service1.foo.example.com" which is not publicly available but can still get certs from letsencrypt, but with a token that can't be used to issue certs for other domains.<p>It works great!
I signed up and saw they only allowed a single subdomain for DDNS, with docs saying to contact support if you needed more. I emailed asking for just 1 more subdomain and support told me that for my usecase I should just use CloudFlare.<p>So I did. No silly miniscule restrictions.
I had this issue with cloudns and a single record with an IPv4 and IPv6 address. They only allowed one free ddns record which covered exactly one protocol. On top of that, they added records to resolve unknown names for advertising purposes.<p>I get that it costs money to run a DNS service but it seems like it should be a lot cheaper at scale than a lot of companies are providing.
Similar story: asked for an increase and got told<p>> […] our mission is to improve Internet security by increasing the adoption of DNSSEC. [We therefore expect users to enable DNSSEC for their domains.<p>> Would you be willing to do that?<p>Wanting to increase the adoption of DNSSEC is fair, but couldn’t this be all self-serve? It’s almost as if they don’t want people to use them.
When I last tried deSEC, the service was reliable and well worth the price of admission, but the web UI and API were both quite rough, and propagation tended to be quite slow. It was annoying to do an ACME DNS01 challenge on it, for example. IIRC, the API didn't have a complete set of replace/edit endpoints, so even DNSControl (<a href="https://github.com/DNSControl/dnscontrol" rel="nofollow">https://github.com/DNSControl/dnscontrol</a>) would leave records nonexistent for a while while during updates.<p>As an aside (though this certainly applies to deSEC) it's strange to me how so many DNS services (free or paid) struggle to import simple Bind zone files, often either giving a vague error ("one or more records could not be imported"), mangling records, or even just silently omitting records. Parsing a zone file has some gotchas, but it doesn't seem like it should be <i>that</i> hard.
I literally just switched away from Hurricane Electric to deSEC. The only real issue that I had with HE, but it's a big one, is that they don't allow wildcard CNAMEs. I consider that important for the security of some sensitive endpoints that I have no choice but to expose publicly. Those endpoints are well protected with 2FA and heavily monitored, but I wanted to be able to use randomized subdomains to at least have some obfuscation on top.
Recently migrated to deSEC, great experience so far, except for hitting the API rate limit when using Tofu to plan and apply changes with around a 100 domains. For now I'm using `-parallelism=1` which seems to work.
We found deSEC to be the only affordable DNS supplier in the EU that complies with state of the art secure DNSSEC. Highly recommended.
DNSSEC support is an anti-feature, it is dead/dying and the faster we can unburden ourselves from it the faster we can move on to better solutions.<p><a href="https://sockpuppet.org/blog/2015/01/15/against-dnssec/" rel="nofollow">https://sockpuppet.org/blog/2015/01/15/against-dnssec/</a>
Rebuttal: <<a href="https://easydns.com/blog/2015/08/06/for-dnssec/" rel="nofollow">https://easydns.com/blog/2015/08/06/for-dnssec/</a>>
That rebuttal held water 10 years ago, but fortunately we have made a lot of advancements since then.<p>DNSSEC was a solution trying to solve the problem of DNS security while still maintaining transparency for DNS operators to spy on queries. At the time, passive DNS was one of the tent poles of tracking malware and responding to security incidents.<p>We have since committed entirely to transport security in the form of DoH and friends. It solves the vast majority of problems we actually have.
Such as? And do those solve the same thing? The post lists 8 headlines why it should be abolished.
So DNS should be open to MITM attackers?
> We found deSEC to be the only affordable DNS supplier in the EU that complies with state of the art secure DNSSEC.<p>I mean, if your definition of "affordable" is free, then sure.<p>But for the record there are other affordable EU suppliers who do DNSSEC:<p><pre><code> - Bunny DNS[0] is "free" – i.e. only subject to their minimum $1/month account spend fee.
- RcodeZero is very affordable[1] plus added bonus it is run by the `.at` registry so the infrastructure is solid – business customers only, no private individuals
- Netnod (only via resellers[2] unless you are a big company or government) – Netnod host the I Root Servers and their public hosting DNSSEC service will soon feature HSM-bound DNSSEC keys
</code></pre>
[0] <a href="https://bunny.net/dns/" rel="nofollow">https://bunny.net/dns/</a>
[1] <a href="https://www.rcodezero.at/solutions/enterprise" rel="nofollow">https://www.rcodezero.at/solutions/enterprise</a>
[2] <a href="https://www.netnod.se/dns/find-a-partner" rel="nofollow">https://www.netnod.se/dns/find-a-partner</a>
I happen to run an affordable EU supplier who does DNSSEC, and also AXFR (incoming and outgoing). I offer a free plan from time to time, but not at the moment to preserve resources for paying customer.<p><a href="https://www.ptrdns.net/" rel="nofollow">https://www.ptrdns.net/</a>
We have a support ticket at Bunny that has been open for months precisely because they don’t provide state-of-the-art DNSSEC. We had to move to another provider, as we have a deadline to comply with at the end of this month. I don’t know what the issue is off the top of my head.<p>Netnod.se uses a DNSKEY that is too small on their main domain.<p>Rcodezero.at might indeed be something. Thanks.<p>We donate to deSEC, so it’s not free for us.
One who doesn't is frustratingly Hetzner.
Is this somehow related to the other post about another service shutting down its encrypted DNS?<p><a href="https://news.ycombinator.com/item?id=49568579">https://news.ycombinator.com/item?id=49568579</a><p>Weird timing?
I have been using deSEC for a couple of years without any issues. I mostly just do not want my DNS handled by my registrar so that I can easily transfer domains without worrying about DNS as well, and I do not like how centralized the internet is becoming around Cloudflare.
Happy deSec user, use them for all my domains. Had quick thoughtful replies from Peter if I had any questions.
Seems legit, but how can I trust them to survive if they're not collecting revenue?
After recent US shenanigans why would you spend effort to migrate to yet another Five Eyes controlled service, especially if they do the full "privacy from Germany" circus.<p>What kind of security threat does a migration to such a service actually mitigate?<p>If they were truly a "sovereign EU" kind of project then they'd be on .eu domain, not have security advisors from Virginia, and so on.<p>Nevertheless it's good to see that the decoupling-from-your-allies movement that US citizens have initiated is so scary that they have to set up these kind of fake EU alternatives with some local figureheads.
Just use unbound
My solution was to self-host PowerDNS and then sign up for the free DNS mirroring from hurricane electric. That way, I can administer my DNS records any way I want (these days I usually just manually edit PowerDNS's sqlite database) and if/when my PowerDNS server goes down, hurricane electric is still serving my records so the domain keeps resolving fine.
Completely different thing
Homepage looks busted on Orion iOS. Signup form has you entering your email address within the yellow “Create Account” button.
Does not support AXFR :(
do what's best.