egg <-> chicken problem

Hello, I've got this running on a system, where the L4 forwarding is use to forward to the DNS server running a domain that is _also_ used by the websites in caddy. As caddy resolves TLS certs on startup, this leads to the following problem: - dns can't be reached because caddy hasn't started - caddy is processing acme challenges - LE can reach the dns, because caddy is still starting - rinse - repeat some sort of 'start L4' first no matter what would be nice, or say to caddy 'resolve' tls in the backgroud. BTW thanks for the L4 stuff, really nice to see that working! :+1: