Use the record editor to connect your domain to hosting, mail and verification services. Work from the values supplied by the service you are connecting. A plausible-looking IP address or mail hostname is not a substitute for its actual configuration.
IN THIS ARTICLE
01 Add a record
- Open the correct domain in DNS Manager and select DNS records.
- Read the current nameserver status and check that the zone is writable.
- Select Add record and choose the required record type.
- Enter the name. Use
@for the domain itself, or a label such aswww. Check the full hostname preview. - Complete the fields shown for that type. An A record needs an IPv4 address, AAAA needs IPv6, CNAME needs another hostname, and MX needs a mail hostname with a priority.
- Choose a permitted TTL or keep the supplied default. Save and review any validation message.
For example, a service may ask for an A record at @ and a CNAME at www. Enter its real address for the A record. Documentation addresses such as 192.0.2.10 are examples and will not make your website work.
02 Edit an existing record
Search by name or value, filter by type if useful, and select Edit on the exact row. Record the old value before saving. When replacing an address, check whether an AAAA record also directs IPv6 visitors elsewhere. Editing only A can leave different visitors reaching different servers.
03 Delete with the owning service in mind
Select Delete only when you know what the record does. Removing an MX record can interrupt incoming email. Removing a validation TXT record may affect certificate renewal or third-party verification. A forwarder-owned record should be changed through its forwarding screen. Provider-managed SOA and protected records may be unavailable for direct editing.
How do I confirm that my DNS record change is working?
Saved changes pass through validation, provider application and readback. A pending or applying status means the work has not yet been confirmed. Refresh the record list, then check propagation and the actual website or mail service. Public caches can retain the previous answer for its earlier TTL. If an operation fails, read its history entry before resubmitting so that you do not create a second unwanted record.