Can Technitium DNS replace Caddy as a reverse proxy?

I’m trying to figure out whether Technitium DNS can handle both my internal DNS and reverse-proxy functionality.

My current setup looks like this:

• All of my services run in Docker.
• None of the application containers expose ports directly to the Docker host.
• I have Technitium DNS running in Docker, with its DNS ports exposed to the host.
• I have a zone configured in Technitium for mydomain.com.
• I use a wildcard DNS record so that *.mydomain.com resolves to my Caddy container.
• Caddy then acts as the reverse proxy and routes requests based on the hostname.

For example:

actual.mydomain.com ↓ Technitium DNS ↓ Caddy ↓ actual:5006 

So Caddy sees actual.mydomain.com and proxies the request to the actual Docker container on port 5006. I have similar configurations for my other services.

What I'm wondering is whether I could remove Caddy entirely and have Technitium handle the routing directly.

Ideally, I'd like something like:

actual.mydomain.com ↓ Technitium DNS ↓ actual:5006 

Can Technitium DNS function as a reverse proxy in this way, where it routes different subdomains to different Docker services/ports?

I'm also wondering about TLS certificates. My domain is managed through Cloudflare. Can Technitium obtain and automatically renew proper TLS certificates (including wildcard certificates) for my domain, similar to how Caddy can with the Cloudflare DNS challenge?

If there's a better architecture for a Docker homelab like this, I'd also be interested in hearing how others have set theirs up.

Thanks