Nameservers are implemented as objects in order to enable registrars to operate on them in a way that reflects their business processes.
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:
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
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.
Nameserver objects can be modified in one of two ways: