DNS

Where DNS lives

DNS connects your domain to services. The registrar manages the domain registration; the authoritative nameservers decide which DNS records visitors use. These can be different providers.

Open Domains → My domains, select the domain and check its nameservers. If it uses another provider’s nameservers, edit records there. Before making changes, save a copy of the existing zone and note which records belong to your website, email and verification services.

Record types

• A: points a hostname to an IPv4 address.
• AAAA: points a hostname to an IPv6 address. An old AAAA record can send some visitors to the wrong server even when the A record is correct.
• CNAME: points one hostname to another hostname. Follow the provider’s instructions for the exact name and target.
• MX: identifies the mail servers receiving mail for the domain, including their priorities.
• TXT: holds text such as ownership verification or mail authentication settings. Copy the supplied value exactly.

@ commonly represents the root domain; www is a separate hostname. Use the format requested by the DNS screen. Example names in these guides are illustrations, not records to copy into your account.

Connect a website

1. Get the exact address or record values from the service you are connecting.
2. In the domain’s DNS screen, review an existing record before adding a duplicate. Change only the hostnames you intend to move.
3. For Splash Builder, open Web address. Select a domain you own and choose Connect for me when offered. Otherwise, add the records displayed by Builder at your DNS provider.
4. For hosting, use the address given during setup or in the hosting instructions. Do not copy an IP address from a screenshot or a different customer’s setup.
5. Save, then check the service’s status and open the live website once HTTPS is ready.

Connect email

Get the current MX and authentication records for your email service. Preserve records for any other legitimate sender, such as a newsletter or invoicing provider. Changing the website’s A record does not require deleting its MX or TXT records.

For SPF, reconcile authorised senders into the correct configuration rather than adding conflicting SPF policies. For DKIM, use the selector and value supplied by the mail service. Follow the supplied DMARC settings and ask for help if you are combining providers. Send a test message to an external inbox and reply from that inbox after the change.

Nameservers and DNSSEC

A nameserver change moves control of the entire DNS zone. Prepare website, email and verification records at the new provider before switching. Existing DNS caches can continue serving old answers until they expire, so keep the old services working during the transition.

DNSSEC also needs the registrar’s DS record to match the DNS provider. The workspace shows DNSSEC instructions and the DS details when applicable. Before disabling DNSSEC or changing providers, follow those instructions and remove or update the old DS record as required. Ask support before proceeding if you are unsure: a mismatch can make the whole domain fail to resolve.

Troubleshooting

Check the domain on another network, then compare the authoritative nameservers and the exact record name, type and value. Verify both www and the root address if you use them. Avoid repeated record changes while you are waiting for caches to expire; note the time of each change instead.

Website works but mail fails: check MX and authentication records. Some visitors see the wrong website: look for conflicting A or AAAA records. Nothing resolves after a nameserver change: check zone completeness and DNSSEC. Send support the domain, intended destination, changed records and error message, with secrets removed.