News for hackers. Stuff that matters.
Re:You Can Run a DNS Server by gerdesj on Saturday March 21, 2026 @07:49PM (#47472797)
I've run DNS servers in the past - BIND and pdns. I've now gone all in ... because ... well it started with ACME.

As the OP states you can get a registrar to host a domain for you and then you create a subdomain anywhere you fancy and that includes at home. Do get the glue records right and do use dig to work out what is happening.

Now with a domain under your own control, you can use CNAME records in other zones to point at your zones and if you have dynamic DNS support on your zones (RFC 2136) then you can now support ACME ie Lets Encrypt and Zerossl and co.

Sadly certbot doesn't do (or it didn't) CNAME redirects for ACME. However, acme.sh and simple-acme do and both are absolutely rock solid. Both of those projects are used by a lot of people and well trod.

acme.sh is ideal for unix gear and if you follow this blokes method of installation: https://pieterbakker.com/acme-sh-installation-guide-2025/ usefully centralised.

simple-acme is for Windows. It has loads of add on scripts to deal with scenarios. Those scripts seem to be deprecated but work rather well. Quite a lot of magic here that an old school Linux sysadmin is glad of.

PowerDNS auth server supports dynamic DNS and you can filter access by IP and TSIG-KEY, per zone and/or globally.

Join the dots.

[EDIT: Speling, conjunction switch]

Re:You Can Run a DNS Server by 9dev on Sunday March 22, 2026 @04:54AM (#47475657)
Seconded. Don’t use certbot; it’s an awful piece of user-hostile software, starting from snap being the only supported installation channel. Everything it does wrong, acme.sh does right.
Re:You Can Run a DNS Server by tryauuum on Wednesday March 25, 2026 @01:55AM (#47513810)
just installed yesterday the certbot on ubuntu 24.04, from the default repos, without any snaps
Re:You Can Run a DNS Server by mediumsmart on Wednesday March 25, 2026 @02:20AM (#47513943)
same on debian trixie. certbot works fine for me. Zone records in bind, generate the dnskey, cronjob to re-sign it daily and your off to the races. no problems no snaps.
Re:You Can Run a DNS Server by locknitpicker on Wednesday March 25, 2026 @03:03AM (#47514200)
> starting from snap being the only supported installation channel.

This sounds like you are complaining about Ubuntu, not the software you wish to install in Ubuntu.

Re:You Can Run a DNS Server by jcgl on Wednesday March 25, 2026 @05:57AM (#47515308)
Unfortunately, it's more than that: the Linux installation instructions on the certbot website[0] give options for pip or snap. Distro packages are not mentioned.

[0] https://certbot.eff.org/

Re:You Can Run a DNS Server by pgporada on Wednesday March 25, 2026 @06:34AM (#47515540)
Make a PR or an issue on the project.
Re:You Can Run a DNS Server by jcgl on Wednesday March 25, 2026 @06:45AM (#47515601)
I feel no need to. I'm quite certain that the certbot folks are aware of the existence of distro packages and even know how to check https://pkgs.org/download/certbot for availability. One might guess that they only want to supply instructions for upstream-managed distribution channels rather than dealing with e.g. some ancient version being shipped on Debian.
Re:You Can Run a DNS Server by adiabatichottub on Wednesday March 25, 2026 @12:24AM (#47513215)
I'm a fan of uACME:

https://github.com/ndilieto/uacme

Tiny, simple, reliable. What more can you ask?

Re:You Can Run a DNS Server by DaSHacka on Wednesday March 25, 2026 @12:35AM (#47513285)
Neat, I've used lego (https://github.com/go-acme/lego) but will certainly have to give uacme a look, love me a simple ACME client.

acme.sh was too garish for my liking, even as a guy that likes his fair share of shell scripts. And obviously certbot is a non-starter because of snap.

Re:You Can Run a DNS Server by adiabatichottub on Wednesday March 25, 2026 @12:49AM (#47513386)
Certbot has earned my ire on just about every occasion I've had to interact with it. It is a terrible program and I can't wait to finish replacing it everywhere.

The new setup is using uAcme and nsupdate to do DNS-01 challenges. No more fiddling with any issues in the web server config for a particular virtual host, like some errant rewrite rule that prevents access to .well-known/.

Re:You Can Run a DNS Server by Spivak on Wednesday March 25, 2026 @06:35AM (#47515546)
I mean certbot handles the just issue me a cert via DNS-01 and I'll do the rest flow just fine. Massive overkill of a program for just that use-case but it's been humming along for me for years at this point. What's the selling point for uACME?
Re:You Can Run a DNS Server by catlifeonmars on Wednesday March 25, 2026 @08:29AM (#47516450)
Lego is solid. I use it with Route53 to do automatic renewal of LE certs for various endpoints before the certs expire.
Re:You Can Run a DNS Server by dwedge on Wednesday March 25, 2026 @04:38AM (#47514803)
> don't expect it to automatically set up your webserver to use the certificates it obtains.

This makes me so happy. Acme and certbot trying to do this is annoying, Caddy trying to get certs by default is annoying. I ended up on a mix of dehydrated and Apache mod_md but I think I like the look of uACME because dehydrated just feels clunky

Re:You Can Run a DNS Server by est on Wednesday March 25, 2026 @10:16AM (#47517656)
I ended up vibe an ACME client for my custom TLS server.

It's a chat server but with curl. You can try it here

curl -NT. https://chat.est.im/hackernews

(Note: IPv6 only for the moment)

Re:You Can Run a DNS Server by jonjoy on Wednesday April 01, 2026 @07:18PM (#47607875)
Devops here. It's not only simple, it's rock solid. It puts all other ACME clients to shame.
Re:You Can Run a DNS Server by ozim on Wednesday March 25, 2026 @02:49AM (#47514109)
I think CNAME redirections being not supported is reasonable choice. Would make my life easier as well but it opens all kinds of bad possibilities that bad actors would definitely use.
Re:You Can Run a DNS Server by dwedge on Wednesday March 25, 2026 @04:41AM (#47514821)
Can you give me an example where this is a problem? If someone can create a CNAME they can create a TXT (ignoring the possibility of an API being restricted to just one).

Without CNAME redirect I wouldn't be able to automatically renew wildcard ssl for client domains with dns that has no API. Even if they do have an API, doing it this way stops me from needing to deal with two different APIs

Re:You Can Run a DNS Server by rdevilla on Wednesday March 25, 2026 @07:32AM (#47515951)
GP comment is just vague distilled model AI slop.
Re:You Can Run a DNS Server by ozim on Thursday March 26, 2026 @03:05AM (#47527425)
I don’t need a crutch I am perfectly capable of writing vague slop on my own thank you.
Re:You Can Run a DNS Server by ozim on Thursday March 26, 2026 @03:08AM (#47527454)
People forget configurations and CNAME can be left when domain it was pointing to changes owner. Then someone unauthorized can make certs for not his domain.
Re:You Can Run a DNS Server by dwedge on Thursday March 26, 2026 @05:17AM (#47528234)
Ok I asked for an example and you provided one, that's fair. It also makes the second domain a target.

I had someone issue a cert on one of my subdomains because I forgot to remove DNS after cancelling a VPS, and the VPS provider didn't remove the reverse DNS so they found it. Small attack, but it happened.

Re:You Can Run a DNS Server by rdevilla on Wednesday March 25, 2026 @05:03AM (#47514987)
> Sadly certbot doesn't do (or it didn't) CNAME redirects for ACME.

Are you certain? Not at a real machine at the moment so hard for me to dig into the details but CNAMEing the challenge response to another domain is absolutely supported via DNS-01 [0] and certbot is Let's Encrypt's recommended ACME client: [1]

    Since Let’s Encrypt follows the DNS standards when
    looking up TXT records for DNS-01 validation, you can
    use CNAME records or NS records to delegate answering
    the challenge to other DNS zones. This can be used to
    delegate the _acme-challenge subdomain to a validation
    specific server or zone.
... which is a very common pattern I've seen hundreds (thousands?) of times.

The issue you may have run into is that CNAME records are NOT allowed at the zone apex, for RFC 1033 states:

   The CNAME record is used for nicknames. [...] There must not be any other
   RRs associated with a nickname of the same class.
... of course making it impossible to enter NS, SOA, etc. records for the zone root when a CNAME exists there.

P.S. doing literally fucking anything on mobile is like pulling teeth encased in concrete. Since this is how the vast majority of the world interfaces with computing I am totally unsurprised that people are claiming 10x speedups with LLMs.

[0] https://letsencrypt.org/docs/challenge-types/

[1] https://letsencrypt.org/docs/client-options/

Re:You Can Run a DNS Server by jcalvinowens on Wednesday March 25, 2026 @11:07AM (#47518366)
I tried this too a couple months ago, OP is right, certbot doesn't support the CNAME aliases: it lacks logic to add the TXT record to the redirected name, instead of the name in the certificate.

I use acme.sh which does support it: https://news.ycombinator.com/item?id=47066072

Re:You Can Run a DNS Server by rdevilla on Wednesday March 25, 2026 @11:50AM (#47519018)
I still find this hard to believe without some actual example RRs and certbot configs, but this is HN, not serverfault.
Re:You Can Run a DNS Server by jcalvinowens on Wednesday March 25, 2026 @12:29PM (#47519593)
I remember being annoyed because the docs don't actually say you can't do it: https://certbot-dns-rfc2136.readthedocs.io/en/stable/

...but they also don't say how to specify the zone to be updated like acme.sh does: https://github.com/acmesh-official/acme.sh/blob/master/dnsap...

So say you want a cert for *.foo.com, and you have:

    _acme-challenge.foo.com CNAME _acme-challenge.foo.bar.com
...I can make certbot talk to the foo.bar.com DNS server, but it tries to add the TXT record for _acme-challenge.foo.com, which that DNS server obviously rejects (and even if it accepted it, that obviously wouldn't work).

I'd be happy to hear there's a way to do it that I missed. Also I'm specifically talking about the rfc2136 support, maybe some of the proprietary certbot backends do support this.

EDIT: Here are more references:

https://github.com/certbot/certbot/issues/6566

https://github.com/certbot/certbot/pull/5350

https://github.com/certbot/certbot/pull/6644