[Feature Request] Built-in DNS Manager (starting with Cloudflare)

What problem will this feature address?

Right now, when I deploy an app with Dokploy, managing DNS records is a completely separate workflow I have to jump over to my DNS provider's dashboard, navigate to the right zone, and manually create or update records. It breaks the flow and adds friction, especially when I'm spinning up multiple services.
I'd love to see a built-in DNS Manager inside Dokploy's settings, so I can handle DNS records without ever leaving the panel.

Describe the solution you'd like

What it would look like

• A new DNS Management section under Settings.
• Connect your DNS provider (Cloudflare to start, with others down the road) by entering your Account ID and an - API Token with Zone Read + DNS Edit permissions.
• Browse your zones, a dropdown listing all domains on your account.
• View, create, edit, and delete DNS records directly from a table inside Dokploy : A, AAAA, CNAME, TXT, MX, and NS types.
• Toggle Cloudflare proxy on/off per record with a simple switch.
• Search and filter records by name or type so you can find what you need quickly even on large zones.
  A status badge showing whether the provider is configured and healthy, plus a last-synced timestamp so you know the data is fresh.

Would love to see this land in a future release. Happy to discuss the design or help test it

Describe alternatives you've considered

The most obvious alternative is just keeping DNS management external opening your Cloudflare (or other provider) dashboard in a separate tab whenever you need to add or update a record. It works, but it completely breaks the deployment flow. Every time you spin up a new service in Dokploy, you're context-switching out of the panel just to point a subdomain at it.

Additional context

No response

Will you send a PR to implement it?

Yes

The issue names no files, tests, or entry points, so first map Dokploy’s settings and DNS-related surfaces before proposing an implementation. Define the Cloudflare connection, zone and record operations, filtering, proxy control, health status, and sync timestamp, then validate the design and acceptance criteria with maintainers.