Decide what the delegation should cover

A subdomain can have its own DNS zone, managed separately from the zone for the main domain. For example, a team running an application at app.example.com might manage DNS for app.example.com while another team continues to manage example.com. This arrangement is called delegation. It changes who answers DNS queries for that branch of the name; it does not transfer ownership of the registered domain or automatically grant access to the parent zone.

Choose the boundary carefully. Delegating app.example.com gives the child-zone operator control over app.example.com and names beneath it, such as api.app.example.com. It does not give them control over www.example.com. If the application needs records at names outside the delegated branch, the parent-zone team will still need to manage those records. Agree on the exact name and responsibilities before making changes, especially if the two teams use different DNS providers.

Prepare the child zone before changing the parent

First, create a DNS zone for the exact subdomain at the provider that will manage it. The provider should supply authoritative nameserver hostnames for that zone. Add the records the application needs, such as address records for its web host and any relevant verification or email-related records. The child zone will also have its own NS and SOA records, generally created by its DNS provider. Check the provider’s instructions before editing those records.

Review any records already published in the parent zone at or below the planned delegation point. Records for names beneath the new boundary may need to be recreated in the child zone so they remain available after delegation. Pay particular attention to service-discovery and verification records, which can be easy to overlook. Keep a written list of the expected names and values without including passwords, private keys, or other credentials.

If the subdomain currently receives email, account for its MX records and related TXT records before switching. Delegation does not copy them into the child zone. Likewise, creating a child zone alone does not make it reachable through normal DNS lookups: the parent must point to its nameservers. Preparing the child first helps avoid a gap between those two steps.

Publish the delegation in the parent zone

In the DNS zone for example.com, add NS records at app.example.com pointing to the authoritative nameservers supplied for the child zone. Use the nameserver hostnames, not the address of the website. Keep the set in the parent aligned with the nameservers configured for the child zone. A DNS provider’s interface may call this action “delegate subdomain” or may require you to add NS records manually.

Do not treat an NS delegation as an ordinary record for the application. Once the boundary is in place, application records for app.example.com and its descendants belong in the child zone. If the parent already has an address or TXT record at the exact delegation name, review it rather than assuming it will continue to work as before. Where DNSSEC is enabled, ask both providers what is needed before adding or changing a DS record; a mismatched DS record can prevent validating resolvers from answering for the child zone.

Nameserver hostnames located inside the delegated subdomain can require additional address information in the parent, often called glue. Using nameservers supplied under a provider’s separate domain usually avoids that particular setup task. Follow the relevant provider instructions if your arrangement requires glue, and avoid changing the parent’s nameservers for the entire domain when you intend to delegate only one subdomain.

Verify the result and assign ongoing responsibility

Check that each child nameserver answers for the intended zone and returns the expected records. Then check that the parent zone publishes the intended NS records at the delegation name. Finally, test ordinary lookups for a few important hostnames beneath it. These checks answer different questions: a working child zone does not prove the parent points to it, and a correct parent delegation does not prove the child contains the records your service needs.

Some resolvers may temporarily show older answers because they have cached previous DNS data. If results differ, compare the parent delegation and direct answers from the child nameservers before changing records again. Avoid using a single successful website load as the only test; it may not reveal a missing record for another service.

Record which team controls each zone, where changes should be requested, and who will review nameserver or DNSSEC changes later. If the child provider or team changes, update the child zone and parent delegation as a coordinated task. A small, clearly documented boundary makes it easier to manage the subdomain independently without losing track of how it connects to the rest of the domain.

Back to category ↗