इसे छोड़कर कंटेंट पर जाएं

Custom domain FAQ

यह कंटेंट अभी तक आपकी भाषा में उपलब्ध नहीं है।

Almost always because at least one record is not visible to us yet. Give it up to an hour before treating it as a problem. If it is still pending after that, re-read the two records against the Domains page character by character - a missing letter in the value, or your domain typed twice into the name field, accounts for most of them. The page names the record it cannot see, which tells you which of the two to look at.

It says the record cannot be found. What does that mean?

Section titled “It says the record cannot be found. What does that mean?”

It means we asked DNS for that exact name and got nothing back. The message includes the full name we looked for, so compare it with what your registrar now shows. The usual cause is the name field, most registrars add your domain to whatever you type, so entering the full name produces something like shop.brand.com.brand.com. Paste the name we show, then check how your registrar displays the saved record.

Connect the one you want shoppers to see; they are two different names here and connecting one does not connect the other. A store holds one domain at a time, so the way to serve both is to connect your choice and then set up a redirect at your registrar from the other to it. Most registrars offer that as forwarding, and it costs nothing.

Not if you add the records instead of replacing anything. Email is delivered by its own separate records, and nothing we ask for touches them. The one case that does break email is deleting or overwriting an existing record while adding ours - which happens most often when connecting a bare domain, because the field looks already taken. If you are unsure, copy your current records into a note before you change anything.

No. It keeps working and redirects to your domain, so older links, printed material and anything a customer bookmarked still reach your store.

How do I move the domain to a different store?

Section titled “How do I move the domain to a different store?”

Disconnect it from the store that has it, then claim it on the other one. It has to be done in that order, a domain that is live on a store is never taken from it, which is what stops anyone else claiming a name you are using. Your DNS records can stay exactly as they are, but the new store issues its own ownership value, so replace that one record with the value the new store shows.

Disconnect it on the Domains page. Your store goes back to its Posty5 address immediately, on the next request a shopper makes. Afterwards you can tidy up the records at your registrar at your leisure - leaving them costs nothing except that the name no longer leads anywhere useful.

My browser shows a certificate warning on the domain. Is something wrong?

Section titled “My browser shows a certificate warning on the domain. Is something wrong?”

During setup this is expected. The certificate is only requested after your records are confirmed, so a domain that is resolving but not yet secured has no certificate for a browser to trust. Wait for the page to report the domain as active and then reload. A warning that persists after that is worth reporting, and the status on the page will say which half is unfinished.

The page gives the reason, and there are only a few. The name is already live on another store; your store already has a domain, so disconnect that one first; the name is a Posty5 address or sits underneath one, which cannot be claimed as a custom domain; or what you typed is not a valid host once tidied up. A refusal happens before anything is created, so nothing needs undoing.

It was working and now the store is back on the Posty5 address. What happened?

Section titled “It was working and now the store is back on the Posty5 address. What happened?”

A live domain is re-checked periodically, including the ownership record, and a domain whose records have genuinely gone stops being served - that is deliberate, because a name that is no longer pointed at us should not keep showing your store. The usual cause is a record deleted during unrelated DNS tidying, the ownership record most often, since it looks like leftover machine noise. Put it back and the domain recovers by itself.