3 ms·

So let's look at this situation. It's a shop page, shop.{clientdomain}.tld. Now you need SSL for this, using AWS you need a TXT record from their ACM. You also

by jabart 4y ago

So let's look at this situation. It's a shop page, shop.{clientdomain}.tld. Now you need SSL for this, using AWS you need a TXT record from their ACM. You also need a CNAME to your domain (ideally) or to a Cloudfront instance. For your customer you now need them to make 2 DNS entries. This is from my experience having non-profit like entities setup DNS. - Well the person who set that up stopped responding, isn't there another way to get this going? - I've added all the record in what do you mean they don't match? - I don't even know what DNS is, why is this necessary? - I added in the record but the system didn't take one of them because it started with an underscore and they said that was invalid. - We just switched websites to WIX, why is our shop page not loading, is your system down? - Will this break my email, I don't want it to break my email. - Here is my login, just go in and change what you need. So in all, it's not just $10, it's a significant investment in time and resources to do this "simple" change that until this point did not have any downside. Hindsight is like that every time.

snowwrestler 4y ago
No, you automate all this on behalf of your clients. The customer is not registering the domain and managing DNS, you are. The best reason not to do full domains is the risk of bad actors re-registering domains you release, as schroeding points out in another reply.
- jabart 4y ago
  Now the customer has two domains and we have been training users to look for signs of phishing attempts using look alike domains AND ask them to put in their CC to buy things. Hard pass.
  - snowwrestler 4y ago
    The customer would already have had two domains because the subdomain was off the SaaS domain, not the client domain. Client.SaaSdomain.tld not Shop.clientdomain.tld If you’re setting up your service as a subdomain off the client domain, you won’t face the risk that one customer will get your entire service domain blocked (since it’s the customers domain).
  - luckylion 4y ago
    > Now the customer has two domains and we have been training users to look for signs of phishing attempts using look alike domains AND ask them to put in their CC to buy things They already have to do that, only currently they have to put it into customername.shop-saas.com, not customername-shop.com, or even shop.customername.com.

by jabart 4y ago

snowwrestler 4y ago

No, you automate all this on behalf of your clients. The customer is not registering the domain and managing DNS, you are. The best reason not to do full domains is the risk of bad actors re-registering domains you release, as schroeding points out in another reply.

jabart 4y ago
Now the customer has two domains and we have been training users to look for signs of phishing attempts using look alike domains AND ask them to put in their CC to buy things. Hard pass.
- snowwrestler 4y ago
  The customer would already have had two domains because the subdomain was off the SaaS domain, not the client domain. Client.SaaSdomain.tld not Shop.clientdomain.tld If you’re setting up your service as a subdomain off the client domain, you won’t face the risk that one customer will get your entire service domain blocked (since it’s the customers domain).
- luckylion 4y ago
  > Now the customer has two domains and we have been training users to look for signs of phishing attempts using look alike domains AND ask them to put in their CC to buy things They already have to do that, only currently they have to put it into customername.shop-saas.com, not customername-shop.com, or even shop.customername.com.