Sub-domain of the apex domains

A sub-domain of an apex domain exists where one or more records are collected together into a self-contained zone, and delegation records exist in the apex domain. Using the apex domain nhs.uk as the example:

1. A delegation for the sub-domain 'bob' is created within the apex domain 'nhs.uk'.
2. The zone 'bob.nhs.uk' is created with a Start of Authority (SOA) record and a set of Nameserver records. The sub-domain 'bob.nhs.uk' is now established and can have records created within it, for example: 'fred.bob.nhs.uk'

A sub-domain of an apex domain must be at level 3 and below in the DNS hierarchy. In the hierarchy section example, 'bob' is at level 3. 

Sub-domains of the apex domains, and their child records are subject to NHS England Domain and Record Naming standards and guidance.

DHSC agencies and public bodies must get clearance to use the NHS brand before requesting a sub-domain name within the apex domain namespace. Requests must be submitted by the DHSC Digital team.

National organisations wholly owned by the Secretary of State for Health must get clearance to use the NHS brand before requesting a sub-domain name within the apex domain namespace.

It is the responsibility of the trusted domain name administrator within an organisation to renew their claim to each sub-domain each year, and in doing so, ensure that their contact details, and those of the technical contacts are complete and accurate. Failure to do this will result in loss of control and removal of sub-domains.

Sub-domains of the apex domains must be reviewed regularly, and removed immediately they are no longer required.

Empty sub-domains will be automatically removed without notice, although the name will remain registered to the original owning organisation, subject to NHS England Domain and Record Naming standards and guidance.