The Problem
The DNS Made Easy add-on does not allow a subdomain (e.g., [sub-domain.apex-domain.gov.ph]) to be added as a standalone, manageable DNS zone.

The system incorrectly requires that the apex domain ([apex-domain.gov.ph]) be added first. This is impossible for us, as our agency only controls its own subdomain, while the apex domain is managed by a separate central IT authority.

Our Use Case (Why this is a Blocker)
This limitation blocks a standard and secure practice for all federated organizations (governments, universities, corporations):

Separate Management: Our central IT manages the apex domain ([apex-domain.gov.ph]) using their own provider (e.g., Cloudflare).

DNS Delegation: We, as a separate agency, must manage all DNS records (A, MX, TXT, etc.) for our own assigned subdomain ([sub-domain.apex-domain.gov.ph]).

The Goal: The standard, secure solution is for our central IT to "delegate" our subdomain to us by pointing NS records to our chosen DNS provider. We want to use the DME add-on as that provider.

The DME add-on's current limitation makes this secure, standard procedure impossible.

The Feature Request (The Solution)
We request that the DNS Made Easy add-on be updated to allow a subdomain to be added as a primary, independent, and manageable DNS zone.

The system should not reject the subdomain. It should accept it as a new zone and provide the necessary DME nameservers for us to give to our central IT admin to complete the delegation.

Why This is Critical
Enables Security: This is the only way to follow the Principle of Least Privilege in a federated environment.

Unlocks a Key Market: This is a non-negotiable, baseline requirement for any customer that is part of a larger organization.

Follows DNS Standards: This is a fundamental, expected capability of any enterprise-grade DNS hosting service.

Without this, the DME add-on is unusable for a large and critical segment of your target customers.

Thank you for your consideration.