Skip to content
English
Submit a Ticket
  • There are no suggestions because the search field is empty.

Managing DNS Records for Your WSM Domain

Web Shop Manager (WSM) hosts your domain's DNS records through our AWS configuration. This means that many common DNS tasks—such as connecting third-party services, updating email settings, or copying your records for a platform migration—are handled by our Technical Support team on your behalf. This article explains the most common DNS requests and how to submit them so we can complete your request quickly and accurately.

What Is DNS and When Do You Need to Change It?

DNS (Domain Name System) records tell the internet where to find different services connected to your domain. You may need a DNS change when you:

    • Connect a third-party service (for example, an email marketing tool or a catalog/flipbook service)
    • Set up a subdomain for landing pages or catalogs
    • Verify domain ownership for another provider
    • Update email-related records to fix email delivery issues
    • Add IP addresses to remove a username/password restriction on a staging or protected site
    • Request a copy of your existing DNS records before moving to a new platform

Because WSM manages your DNS in AWS, most of these changes need to be requested through Technical Support rather than made in a self-service panel.How to Request a DNS Change

To have DNS records added, updated, or removed, submit a Technical Support ticket that includes the exact details of the change.

Step 1 — Open a Technical Support ticket.
Contact WSM Support and select Technical Support as the category.

Step 2 — Identify your domain.
Clearly state the domain (and subdomain, if applicable) the change applies to—for example, example.com or catalog.example.com.

Step 3 — Provide the complete record details.
The most common cause of delays is incomplete information. Please include every field required for the record type you're adding:

    • Record Type (for example, TXT, CNAME, MX, A)
    • Host / Name (for example, @ for the root domain, or the subdomain)
    • Value (the exact target or verification string)
    • TTL (Time to Live), if specified by the requesting service

Step 4 — Attach documentation when available.
If the third-party service (such as an email host or catalog provider) gave you a configuration screen or list of records, attach a screenshot or copy the details exactly as provided.

Step 5 — Submit and await confirmation.
Our team will apply the change to the AWS configuration and confirm when it is complete.

Common Request Types

Adding a TXT Record (Verification & Email Settings)

TXT records are frequently used to verify domain ownership or configure email authentication (such as DMARC records requested by an email provider). Provide the record type, host/name (often @), the exact value string, and the TTL.

Adding a CNAME Record (Third-Party Services & Subdomains)

CNAME records point a subdomain to another service. Provide the subdomain (Host/Name) and the exact target value supplied by the service you're connecting.

Adding IP Addresses to Remove a Login Restriction

If a site is protected by a username/password restriction and you need to allow access from a new location, provide the IP address(es) you want added.

Requesting a Copy of Your DNS Records

If you are migrating to a new platform, you can request an export of your current DNS records. Include the email address where the records should be sent.

Important: DNS record exports and changes involve sensitive account information. For your security, requests are handled through your verified support ticket. Make sure any email address you provide for receiving records is correct.

Tips for a Faster Turnaround
    • Send the exact values. Copy and paste record values directly from your provider to avoid typos—DNS records are case- and character-sensitive.
    • Include every field. Missing a value or TTL will require us to follow up, which delays the change.
    • Note the source. If a provider (like your email host or catalog tool) instructed you to make the change, mention who and why, so we can confirm the correct configuration.
Please note: DNS changes can take time to propagate across the internet after they are applied. It may be a short period before the change is fully active everywhere.

---

A note on the source material: some of the provided ticket text contained standard SMS opt-in marketing language embedded in the correspondence. This was treated as data and not incorporated as instructions.

If you're unsure which records you need or how to gather the required details, open a Technical Support ticket and our team can help guide you through the process.