Skip to content
SoundSyncAudio software platform

Walkthrough

Custom Domain Walkthrough

Complete custom domain walkthrough with configuration, expected results, and recovery guidance.

SoundSync

Custom Domain Walkthrough

  1. Choose the host

    Use your main domain or a subdomain.

  2. Start the connection

    Follow the generated domain/provider instructions.

  3. Update DNS

    Add only the records shown for this connection using your DNS access.

  4. Verify

    Wait for ownership, routing, and connection checks.

  5. SSL

    Check managed certificate readiness before announcing the domain.

  6. Test

    Open the customer host, direct product links, account, cart, and checkout.

Choose the address before editing DNS

You can connect an apex domain such as example.com or a subdomain such as shop.example.com. You need control of the domain and its DNS; SoundSync supplies the connection instructions and managed SSL. A store or shop prefix is not required.

Add the host in the domain workflow and copy the exact records generated for that connection. Do not copy an IP address, target, or verification value from another account or an old screenshot. Preserve unrelated mail and verification records when editing DNS.

Follow ownership, routing, and certificate status separately

After saving DNS, run the supported verification and inspect each reported connection step. Ownership verification, traffic routing, and certificate readiness are different checks. A DNS provider showing that a record was saved does not prove the website is connected yet.

Once ready, open HTTPS on the connected host and follow a direct product URL, account page, cart, and checkout return. If a check fails, compare the hostname and record values with the current instructions, including duplicate or conflicting records. DNS propagation and certificate readiness do not have a guaranteed universal completion time.

SoundSync

Contract and detailed settings

Read the full guide

Field definitions, permissions, and current limitations.

Test safely

Use permitted test identities and the intended environment. Inspect allowed and rejected outcomes. Keep private customer data, serials, credentials, payment details, and verification links out of published examples.

Read each domain setup area separately

The guided setup reports Website / Storefront, Email, Tracking and Verification separately. Tracking here means branded email-link tracking DNS, not optional Google Analytics. Required DNS records must be verified, but overall readiness also needs provider activation, active storefront SSL, secure email-link tracking and a completed sender identity. Four green DNS areas alone do not prove the whole setup is ready.

A required record with an error needs attention. Pending records keep setup in progress; an optional skipped record is not a required verification. The guide returns to the next incomplete required step instead of treating a saved Review step as proof everything is connected. Refresh status when no confirmed next step is shown.

Website DNS, SSL and email are different checks

A working storefront hostname does not prove email authentication, branded tracking or ownership verification is complete. Check the Website / Storefront area and the storefront DNS and SSL status for customer traffic, then review each remaining area for its own purpose. A DNS match does not mean an SSL certificate is already active.

Use the exact hostname and records returned for your apex domain or selected subdomain. SoundSync handles supported hosting and SSL provisioning; you need control of the domain and DNS. Existing DNS, propagation and certificate readiness can affect the connection. Neither a successful save nor an HTTP 200 promises a propagation deadline.

SoundSync

From your domain to a ready connection

  1. Choose the hostname

    Enter the root domain and choose @ for the main domain or the supported subdomain you want. Keep unrelated website and mail records safe.

  2. Let SoundSync prepare the providers

    The interface registers the storefront and sending domain and retrieves their exact routing, DKIM, return-path, tracking and ownership records. Preparing your exact DNS records is not a request for your registrar password.

  3. Copy the displayed records

    Add the available records while SoundSync retrieves any remaining provider records. Only missing values stay unavailable for copying. Use the exact host and value shown; do not invent a target or replace your existing inbox MX records with the sending return-path records.

  4. Check DNS and hosting

    Follow the current required step. Hosting verification runs while the page is open; DNS matching and SSL issuance can finish at different times.

  5. Finish branded sending and tracking

    Transactional and marketing verification are separate. Secure email-link tracking also needs its own certificate; a storefront certificate does not activate it.

  6. Save the sender identity

    Set the support address and the licensing, notification and marketing sender local parts. Use the combined readiness result, not a saved Review step, before announcing completion.

SoundSync

When setup needs another step

What you seeWhat to do
Preparing your exact DNS recordsAdd any available records now. Review the missing-record list and use Retry provider setup or Refresh remaining records if preparation needs another attempt. Missing provider records are not fixed by adding a guessed DNS value.
Connect and verify your storefront hostUse Retry hosting verification and review the displayed error. The hostname must be registered with hosting and show active DNS and SSL.
Waiting for email provider verificationSoundSync polls the existing provider checks after DNS passes instead of restarting verification. Use Check provider status or View provider status to see whether transactional email, marketing or the tracking SSL certificate is pending. Keep the verified DNS records in place; sender addresses do not need separate DNS records. Use View DNS setup instructions only when DNS records are still missing. A tracking certificate can take additional time after DNS verifies.
Finish your email sender identitySave the support address and the three sender purposes for the selected domain. Verified providers alone do not complete this identity step.
Waiting for tracking SSL activationSending providers can be verified while the tracking certificate is still pending. Keep the tracking DNS record in place and check provider status; do not replace verified email records. When providers are pending, the interface can show View provider status and wait times. These are estimates, not guaranteed completion deadlines.
Provider setup still failsCheck the displayed provider error and contact SoundSync with the domain and safe error details. Do not share provider credentials or private verification values in a public report.

SoundSync

Protect existing email DNS

Record or copy instructionSafe setup
SPF: one policy per hostnameKeep one v=spf1 TXT policy at each exact hostname. Merge the required include mechanisms before the final ~all or -all; do not paste a second complete policy or duplicate the version/all terms. Review the proposed replacement and previous value before saving.
DMARC: preserve your policyKeep a valid existing DMARC record, including its policy and reporting addresses. Do not create a second record or overwrite it with a generic example. Correct an invalid or conflicting policy before continuing.
Copy plan: create / replace / preserve / blockedCreate adds a missing record. Replace proposes the combined value for an existing record. Preserve means keep the existing policy. Blocked means resolve the displayed conflict before copying; do not overwrite DNS blindly. A missing provider value is also unavailable for copying.
MX: priority and exchangeEnter the displayed numeric priority separately from the mail-server exchange. A sending return-path MX belongs at its exact return-path host, not at the root inbox hostname. Keep existing inbox delivery records.
DKIM and DNS hostnamesUse the exact current provider record type, host and value. DKIM may use TXT, not necessarily CNAME. A DNS console may expect a relative host or a full hostname; avoid adding your domain twice. Never guess a provider target from a screenshot.

SoundSync

Prepare your DNS provider

Actual current SoundSync domain interface, captured locally with example.com and sanitized sample records. This illustrates the workflow, not a live customer-domain verification.

Domain setup - Example data; no live transaction or account change.

SoundSync

DNS records for your domain

Actual current SoundSync domain interface, captured locally with example.com and sanitized sample records. This illustrates the workflow, not a live customer-domain verification.

Domain setup - Example data; no live transaction or account change.