Skip to content
Ionia Docs
Esc
navigateopen⌘Jpreview
On this page

Connect your domain

Safely add the DNS records provided for an Ionia site or portal.

Use this guide when connecting a domain or subdomain to an Ionia-managed website, landing page, portal, documentation site, menu, or local-services page.

This guide is for business owners, agency partners, and the person who manages the domain’s DNS.

What You Will Need

Before starting, have the following ready:

  • The DNS instructions supplied by Ionia or your agency.
  • Access to the domain’s DNS provider.
  • The exact domain or subdomain being connected.
  • A contact who can confirm the existing website still works after the change.

Common DNS providers include Cloudflare, GoDaddy, Namecheap, Squarespace Domains, and other domain registrars or hosting companies.

If someone else manages your domain, send them the DNS instructions instead of sharing your password.

Choose What You Are Connecting

A subdomain

Examples:

docs.example.com
app.example.com
offers.example.com
menu.example.com

A subdomain is usually the quickest and lowest-risk option because it does not replace the main website.

The main website

Examples:

example.com
www.example.com

Connecting the main website may replace or reroute the existing site. Schedule this change with Ionia or your agency so the current site, forms, and important links can be checked immediately afterward.

The DNS Records You May Receive

Use the values in your Ionia setup screen or the instructions sent by your agency. Copy them exactly.

Record What it does
CNAME Connects the selected hostname to the Ionia delivery service.
Ownership TXT Confirms that you control the hostname.
SSL TXT Allows a secure HTTPS certificate to be issued.

Not every setup requires every record.

Your instructions will include:

  • Type: usually CNAME or TXT
  • Name or Host
  • Target, Value, or Content
  • Proxy status, when Cloudflare manages the DNS

Do not copy record values from another business or website. Verification values can be unique to your hostname.

Add Records In Cloudflare

  1. Sign in to Cloudflare.
  2. Select the customer’s domain.
  3. Open DNS and then Records.
  4. Select Add record.
  5. Choose the record type shown in the Ionia instructions.
  6. Enter the supplied Name and Target or Content.
  7. For a CNAME, use the proxy status shown in the instructions.
  8. For a TXT record, leave the proxy setting as DNS only. TXT records are not proxied.
  9. Leave TTL set to Auto unless your instructions say otherwise.
  10. Save the record.
  11. Repeat for any additional ownership or SSL record supplied.

Do not guess whether the cloud should be orange or gray. Use the setting shown in your Ionia instructions.

Add Records At Another DNS Provider

The labels vary by provider, but the fields are the same:

  1. Open the domain’s DNS or zone editor.
  2. Select Add record.
  3. Choose the supplied record type.
  4. Enter the supplied host or name.
  5. Enter the supplied target, value, or content.
  6. Leave TTL at its default or automatic value.
  7. Save the record.
  8. Repeat for each additional record supplied.

Some providers automatically add the domain name after the host field. For example, when connecting docs.example.com, the provider may expect only docs in the Host field.

Important Formatting Rules

  • Do not add https:// to a CNAME target.
  • Do not add /, /menu, /docs, or another path to a DNS value.
  • Do not add quotation marks unless the provider adds them automatically.
  • Use @ only when the instructions explicitly refer to the root or apex domain.
  • Do not create duplicate CNAME records for the same hostname.
  • Do not delete the existing website record until the scheduled cutover.

Do Not Change Email Records

Website DNS and email DNS can live in the same account.

Do not remove or modify records labeled:

  • MX
  • SPF
  • DKIM
  • DMARC
  • Google Workspace or Microsoft 365 verification records

Changing these can interrupt business email. If you are unsure whether a record is related to email, leave it in place and ask Ionia or your agency.

Tell Us When The Records Are Saved

After adding the records, notify your Ionia or agency contact.

We will check:

  • Domain ownership verification
  • SSL certificate status
  • Public DNS resolution
  • The correct website or page is attached
  • HTTPS works without a certificate warning

DNS updates can appear quickly, but some providers may take longer to publish them. Avoid repeatedly deleting and recreating correct records while verification is pending.

Confirm The Connection

Once your contact confirms the hostname is ready:

  1. Open the URL in a private or incognito browser window.
  2. Confirm the expected website or page appears.
  3. Confirm the browser shows a secure HTTPS connection.
  4. Check the page on a phone.
  5. Test the primary call, contact form, booking, or order action.
  6. Check important navigation links.

For a main website connection, also confirm that business email still works. Ionia should not require email DNS changes, but this is a useful final check after any DNS work.

If Something Does Not Work

The address cannot be found

The DNS record may not have published yet, or the host/name may have been entered incorrectly.

The browser shows a certificate warning

SSL validation may still be pending. Confirm that all supplied TXT records were added exactly as shown.

The wrong page appears

Do not make additional DNS changes. Send the URL and a screenshot to Ionia or your agency so the hostname can be checked against the correct customer workspace.

The existing website stops loading

Contact Ionia or your agency immediately. If the main website record was changed, restore the previous value from the DNS backup or screenshot captured before the cutover.

What To Send Your Agency Or DNS Manager

When someone else is making the change, send them:

  • The exact hostname being connected
  • Every supplied DNS record
  • The requested launch time
  • Your Ionia or agency contact
  • A reminder not to modify email records

Ask them to confirm when the records are saved. A screenshot of the completed DNS rows is helpful.

Agency Launch Checklist

  • The client approved the hostname.
  • Existing DNS records were captured before editing.
  • The supplied CNAME was added exactly.
  • Any ownership and SSL records were added.
  • Email records were left unchanged.
  • Ionia confirmed domain and SSL status.
  • The correct customer site or page loads.
  • Mobile, forms, booking, ordering, and primary links were tested.
  • The client received the final public URL.

Was this page helpful?