Skip to Main Content

Nominet

Log in to the online service
Skip Primary Navigation
Skip All Secondary and Tertiary Navigation

Print this page  | Contact Us

Nameservers are implemented as objects in order to enable registrars to operate on them in a way that reflects their business processes.

Introduction

Each domain name can have up to ten nameservers associated with it. 

Nameservers do not need to be supplied and if there are none for a domain then the domain will not be built into the relevant zone on our nameservers.

We only carry out basic checks when a nameserver data is supplied:

  • We check to ensure the Top Level Domain (TLD) is a genuine TLD in the IANA root zone and not from any alternate root.
  • We check the syntax of the nameserver conforms to what we believe to be an acceptable Internet host name.
  • We do not check to see if the nameserver exists.
  • We do not check to see if the nameserver is serving the specified zone.

Nameserver objects

Whenever a new domain is registered the registrar chooses whether to assign existing nameserver objects or whether to create new nameserver objects. If a new nameserver object is created then the ID is returned to enable later manipulation.

Each domain has ten numbered slots for nameservers.  To create new nameserver objects, use the fields dns0 ... dns9.  To specify existing nameserver objects, use the fields dns0-id ... dns9-id.

Nameserver objects are associated with a TAG.  They can be applied to any domain name on that tag but cannot be applied to any domain that is not on that tag.  If a domain is moved to another TAG then a copy of the nameserver information is used to create a new nameserver object.

Nameserver objects do not need to point to unique nameservers, even on the same tag. For example I can have two or more nameserver objects, on the same tag, that point to ns1.internet.co.uk

Glue

If a nameserver is used for the same domain in which it is named then the IP address(es) of that nameserver must also be specified. This IP address data is known as 'glue' and without it the nameserver cannot be added to our zones.

For example, if the nameserver ns1.internet.co.uk is used as the nameserver for internet.co.uk then the IP address must be supplied.

Glue can be supplied even when not needed but we do not use it. It is not added to the zone.

Modifying nameserver objects

Nameserver objects can be modified in one of two ways:

  • Using the nameserver MODIFY operation by specifying the id(s) of the nameserver object(s) to change. This will modify the nameserver directly, irrespective of how it may be used by its parent domains or account.
  • Using the MODIFY operation and specifying the fields that refer to the numbered nameserver slot. For example modifying 'dns0' or 'dns1'.

Nameserver consolidation

If the nameserver consolidation option is switched on for a tag in online services then rather than creating a new nameserver object when a nameserver is referred to by name in the nameserver modify operation and during domain name or ENUM creation, an existing nameserver matching the details (name and ip addresses) given will be found and used.
 
 
 

© Nominet UK 1996-2008  |  Accessibility  |  Site Map  |  Feeds