Connect your domain last, once the store has passed review. The order is: check the draft page by page and work through the online store launch checklist, add the domain in Setka, create the DNS record exactly as Setka shows it for your store, wait until Setka reports the domain as connected, make it primary, and publish. Then place a real order, refund it, and launch. Never copy DNS values from another store, an article, or an old support message: the record type and target are specific to your store.

This order works because in Setka, connecting a domain and publishing are separate steps. DNS only decides where the address points; your changes reach customers only when you click Publish on the version you approved. With the store already reviewed, launch day comes down to one DNS change and one Publish click, instead of fixing pages while customers can already see them.

The part of DNS you need

A domain such as example.com is the address people type. DNS is the public directory that tells browsers where that address leads. You edit its records at the DNS provider for the domain, which may be the registrar you bought it from or a separate service.

Four terms matter here:

  • Hostname: the address you connect, such as the root domain or the www subdomain.
  • Record type: how the DNS record points that hostname elsewhere. Use only the type Setka shows for this store.
  • Target: where the record points, generated in Setka for this store. Copy it from the current screen in Setka, never from a screenshot.
  • TTL and caching: resolvers keep DNS answers for a while. A changed record doesn’t reach every network and device at the same moment.

Changing the record doesn’t transfer the domain to Setka. You keep the registrar and DNS accounts, the renewal, and every other record, such as the ones that run your email. That also means the DNS change itself is in your hands, so make it carefully.

Prepare the domain account before launch day

Sign in to the registrar and the DNS provider ahead of time. Check that the domain is renewed, that account recovery works, and that two-factor login doesn’t depend on someone who won’t be around. If an agency or whoever set up your email manages the domain, agree with them now who will make the change.

Before editing anything, note the current record you intend to replace: hostname, type, value, TTL, and proxy setting. That note is your way back. Leave unrelated MX, TXT, verification, and mail-authentication records alone. If an old website lives at that address today, visitors stop reaching it once the record points to Setka, so decide what happens to it first.

Also decide which form is primary, the root domain or www, and how the other one should behave. You set both in Setka. Pick one deliberately, because ads, emails, packaging, social profiles, and search listings should all end up using the same address.

The controlled DNS flow

[Approved store preview]
          |
          v
[Add owned hostname in Setka]
          |
          v
[Copy the target Setka shows for this store]
          |
          v
[Create the indicated DNS record at the active provider]
          |
          v
[Wait for the product's connection check] ---> [Wrong or stale answer? Compare with current instructions]
          |                                      ^
          v                                      |
[Confirm the expected connection state]
          |
       connected
          v
[Choose primary when ready]
          |
          v
[Publish approved draft explicitly]
          |
          v
[Test public domain and purchase path]

Connect the domain in Setka

Follow the current screens in Setka rather than a copied walkthrough:

  1. Add the hostname you own in Setka.
  2. Read the record instructions Setka generates for that domain and store. Copy the hostname, record type, and target exactly.
  3. At your DNS provider, change only that record.
  4. Return to Setka and wait for the domain to show as connected. If it doesn’t, compare the record at your DNS provider with the current instructions before changing anything else.
  5. Make the intended domain primary.

Don’t keep changing a correct record because one device still shows the old answer. Check the record at the DNS provider first, then try a different network or resolver. Most resolvers pick up a changed record within the old record’s TTL, usually minutes to a few hours. If Setka still doesn’t show the domain as connected after a day, check the record against the instructions again.

Setka issues a free TLS certificate for the domain automatically; you don’t buy or install one.

Preview first, then publish

A connected domain tells you routing works, not that the store is ready. Before publishing, go through the draft in Setka: the homepage, categories, representative product pages, the cart, and the way into checkout. Switch between desktop and mobile preview, look at long product names and real prices, check that the images you need are in place, and click through the navigation rather than judging the first screen.

Setka builds the store inside the same platform that runs checkout and orders, shows you the draft before anything goes live, and publishes only when you click Publish, so you decide which version goes live. Every version is saved: if you spot a problem after publishing, fix the page and publish again, or go back to an earlier version and publish that. If payments are part of this launch, finish the Stripe and checkout setup before the cutover.

Launch-day checklist

Before changing DNS

  • The store passed desktop and mobile preview with representative products.
  • Prices, stock, shipping, tax settings, contact details, policies, and the cart were reviewed.
  • You know which version you’ll publish, and nobody is still editing it.
  • Registrar and DNS access work, and the current record is noted.
  • The primary form of the domain, and how the other form behaves, are decided.
  • The hostname, record type, and target for this store are open in Setka.

Connect and publish

  • Create only the DNS record Setka indicates, and check it matches the instructions exactly.
  • Setka shows the domain as connected.
  • The intended domain is primary.
  • Look over the approved draft once more, then click Publish.

Check the public store

  • The primary domain loads securely on a separate network, including deeper category and product URLs, not just the homepage.
  • The other form of the domain behaves as you set it in Setka.
  • Homepage, navigation, categories, product pages, cart, and checkout work on desktop and on a real phone.
  • A real order placed on your phone went through and was refunded from the Setka order.
  • Analytics and consent work, if you use them.
  • The primary URL, canonical tags, crawl settings, and sitemap pass the e-commerce SEO checklist.

Only then launch: start sending customers to the store.

If something goes wrong

For the first few hours, check the store from more than one network, because your own connection may still have an old answer cached. Watch the domain status in Setka, checkout and payment outcomes, incoming orders, and customer messages.

If the domain fails, write down what you see before changing anything: the hostname, the time, the network, the error, the status in Setka, and the record at your DNS provider. Compare the record with the current instructions in Setka. If the store can’t stay down, restore the record you noted before the change rather than trying a new target or deleting other records. Then email contact@getsetka.com with your notes; it goes to the people who build Setka’s domain handling.

For everything that comes before this step, from catalog to settings, see how to build an online store. If you haven’t started yet, build your store in Setka, review it in preview, and connect the domain when it’s ready.