What DNS does
DNS connects a domain name to services such as a website or email system. Your authoritative nameservers hold the records that tell other systems where to send requests.
A and AAAA: the website address
An A record points a name to an IPv4 address; an AAAA record points it to an IPv6 address. Use the values supplied by your hosting provider. A record named @ usually refers to the root domain.
CNAME: an alias
A CNAME points one hostname to another hostname. Website providers often request a CNAME for www. Do not put an IP address into a CNAME value, and follow your DNS provider’s rules for root-domain aliases.
MX and TXT: email and verification
MX records identify mail servers and have a priority value. TXT records hold text used for verification and email policies such as SPF, DKIM and DMARC. Copy values carefully: a small error can affect mail delivery.
CAA: certificate permissions
CAA records tell certificate authorities which issuers are permitted for a domain. Use your certificate provider’s exact flags, tag and value. A common shape is 0 issue followed by the quoted issuer name. A restrictive policy or an unsupported critical tag can prevent a new certificate being issued; changing CAA does not revoke existing certificates.
SRV: finding a service
SRV records identify a service host and port. Use a name such as _sip._tcp, enter weight, port and target in the value, and enter priority separately. Lower priorities are tried first; weight selects among equal priorities. Follow your service provider’s instructions. The target needs address records and must not be a CNAME. A target of . states that the service is unavailable.
Make changes carefully
Keep a copy of the existing records, change only what the service provider requests, and test the result. DNS caching means different users can see a change at different times. TTL is the cache lifetime, measured in seconds.
TLSA and SSHFP: service authentication
TLSA associates a service’s TLS certificate or public key with a port and transport, such as _443._tcp.www. Enter usage, selector, matching type and hexadecimal certificate association data from that service. SSHFP publishes an SSH host-key fingerprint at the host name, such as ssh, using key algorithm, fingerprint type and hexadecimal fingerprint. Publishing either record does not enable DNSSEC or check the server’s certificate or key. Authenticated use requires DNSSEC validation and a client that supports it. Coordinate certificate and host-key changes with your service provider before replacing these records.
Keep a copy before moving DNS
In the DNS tab, a JSON snapshot preserves the supplied values for reference. A zone-file download converts supported records to BIND format for hosts that accept it, after NameUK has verified the DNS host’s text format. Both include records outside your current filter. If any record cannot be converted, the zone download stops without skipping it. Check the destination’s file-size and SOA/NS rules, then verify website and email records before changing nameservers. Files do not copy hosting settings, private DNSSEC keys or signing state; plan DNSSEC separately. Sample downloads contain fictional records.
Review a DNS file before adding records
The DNS tab can review a BIND zone file or a NameUK JSON snapshot for the same domain. Select the website, email and service records you want to add. Every file row stays visible: existing values, repeated rows, unsupported types, TTLs and conflicts are explained before confirmation. Unselected rows are not imported. Each selected record is added and checked separately; earlier confirmed additions remain if you stop or a later result is uncertain. Importing does not replace existing records, move nameservers or copy DNSSEC keys. Compare the final records and test website and email services before any DNS move. Sample imports change only fictional records in your browser.
Extension rules and provider processes can change. Check the current registrar instructions before a registration, transfer or renewal.