> The thing that made it click for me is realizing how directives act differently depending on their context/scope (I'm not sure what the right term is). The C

> The thing that made it click for me is realizing how directives act differently depending on their context/scope (I'm not sure what the right term is). The Concepts page explains https://caddyserver.com/docs/caddyfile/concepts#structure https://caddyserver.com/docs/caddyfile/concepts#structure. Essentially, "directives" are top-level things inside of a site block (or things within 'route' or 'handle' as well, which wrap other directives), and things inside directives are "subdirectives", i.e. options/config for directives. Matchers are just matchers. Things inside an "empty" block at the top of the Caddyfile are "global options" (similar relative placement to directives, but can only appear in the global options block at the top). > Maybe you could convince some of the infrastructure providers like Cloudflare to maintain community images with their DNS plugins baked in. We have no contacts at Cloudflare. They'd have to reach out to us, tbh. But I don't think they are likely to see it as a benefit to them to spend the time either. Ultimately, the plugin very rarely changes, it's pretty stable at this point. > Thanks again for taking the time to reply. I'm probably going to set up a custom Docker image and give things another try. If I do and I end up using Caddy, hopefully I can pay it forward at some point :-) Glad to hear. Next time you need help, the forums are the best place to ask. It actually supports markdown, and it's actually meant for Caddy support https://caddy.community/ https://caddy.community/