HSCN/Transition Network DNS


This document provides an overview of DNS on HSCN and TN and the DNS change request process

What is DNS?

The DNS (Domain Name System) allows IP network users to use alphanumeric aliases in place of numeric IP addresses.

For example, a user typing www.nhs.uk into a web browser will get to the website hosted by a server at internet IP address DNS tells the user's computer that www.nhs.uk is actually at IP address The user's computer, the server hosting the website and the network on their own only understand IP addresses.

DNS also lets operators move servers and services to different IP addresses invisibly, whilst keeping the DNS naming the same for users.


nhs.uk is the registered internet domain for the UK National Health Service. This means it is for internet use - for instance, when sending email outside the NHS or when an NHS organisation wants to access a public website. However, the NHS also uses nhs.uk on HSCN, the Transition Network (TN) and its other private networks. 

Using nhs.uk both internally and externally (on the internet) makes the user experience seamless. An HSCN/TN user typing nww.nhs.uk into their browser will get the internal NHS top-level website, but if they type www.nhs.uk they'll get the internet top level website. This is because the TN has a gateway to the internet, but they are different websites on different networks.

nhs.uk is the NHS's top level domain. Individual NHS organisations normally have their own sub-domain of nhs.uk, for example: digital.nhs.uk. Sub-domains are normally just called domains, when they're being talked about alone. A full DNS address (technically known as a URL) includes the hostname prefix; the name of a server where a website is hosted. For example www.digital.nhs.uk identifies the web server called 'www' for the digital.nhs.uk (sub!) domain.

How does DNS work?

DNS works by user (client) computers sending queries to a local DNS server to get the IP addresses they need. This is called resolving. Domain name data is distributed and/or delegated amongst a number of name servers. Often the local name server doesn't hold all the data requested, even though local servers do store (cache) some answers to recent DNS queries. If the answer isn't cached, the local server checks with other name servers to get the data. This is known as recursive operation. This process continues until the definitive DNS information (record) for a domain is found on an authoritative DNS server. Although previous examples have used the nhs.uk domain, the resolving process works for queries about any domain registered and in use. A TN (formerly N3) user DNS request for the IP address of www.mircosoft.com would be resolved in the same way.

Because DNS is so important there should always be at least two DNS servers for any domain for resilience. These are often called primary and secondary, although they may share DNS requests more equally than the names suggest, depending on set up.

HSCN/TN/nhs.uk logical DNS configuration

The below diagram shows the logical DNS configuration used across HSCN/TN


  1. NHS Digital recommend that all TN users continue to use the current provided internal DNS servers shown as their 'local' servers for DNS queries. They are at the following network IP addresses: cns0.nhs.uk ( and cns1.nhs.uk (
  2. The current provision of a Network Time Protocol (NTP) reference source will remain in place for all users to synchronise the clocks in servers and PCs. NTP is currently shown separately in the diagram, however the NTP platform will be refreshed as part of TN services. The reference source is actually available from the same IP addresses (above) as the internal DNS service.

DNS records

Data for a domain, such as nhs.uk, is arranged in zone data files with a number of (resource) records. The most important and most often used are the:

  • address record (A record) - used to direct users to live servers for web browsing and file transfers for example
  • mail exchange record (MX-record) - used to direct messages to email/messaging servers for a domain

Other types of record used on the nhs.uk DNS servers are:

  • start of authority (SOA): defines the start of a zone data file, includes information on: 
    • the name server with ultimate authority for the domain
    • who to contact about the domain
  • name server (NS): defines one or more name servers with definitive DNS information
  • Canonical Name/alias (CNAME): defines additional aliases for an IP address (as alternative to multiple A records)
  • Pointer (PTR): a 'reverse lookup' record that associates an IP address to a DNS name - effectively the reverse of an A record

DNS change request process

nhs.uk DNS records are owned and administered by NHS Digital. NSS in Scotland administers the scot.nhs.uk (sub) domain. The TN provider will continue to manage the 'live' DNS service for the foreseeable future.

DNS change requests, to change either zone data files or individual DNS records, must be made directly to these bodies. The HSCN/TN service provider cannot accept DNS change requests from end-users.

Find England DNS change request forms and contact information

Further information

  1. internal

    HSCN IP address management

    Find all information relating to IP address management under HSCN, including the HSCN IP addressing policy, IP addressing good practice guidelines, IPAM process and change request forms.

  2. internal

    Business Applications Guidance

    This document provides guidance on procuring standard business applications to replace N3 overlays and is aimed at health and social care organisations moving to HSCN from N3.

  3. internal

    HSCN Quality of Service overview

    Quality of Service (QoS) is a set of techniques to manage resources within a communications network. This page provides details of QoS implementation across HSCN.

  4. internal

    HSCN connectivity options

    The Health and Social Care Network (HSCN) programme will provide new and significantly different network services to the N3 network it succeeds.