V2.10.0-beta.1 dns vs acme_dns

I am seeing when I use the new beta 2.10.0 if I have acme_dns configured globally, I also have to set the new dns global directive, otherwise caddy will not start. I do not yet have anything configured for ech, is that expected behavior? I find it slightly confusing that I have to set both global options although nothing changed in my config.

Thanks for trying the beta! Fixed here already:

1 Like

Indeed. But if I use the new version, what do I do with tailscale certificates? I am using cloudflare for all my production endpoints, but internally I have web hooks running on my tailnet. I got the impression, that even though a tailnet acquires its cert via the tailscale daemon, it will now complain about not having a dns global default. But this global default is not authoritative there, is is only for the cloudflare domains. Is there a way to decouple this?

I have just noticed that this might also be the stale go proxy problem. Will build again and see what happens.

This topic was automatically closed after 30 days. New replies are no longer allowed.