Hacker News new | ask | show | jobs
by snowwrestler 1354 days 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.
1 comments
jabart 1354 days 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.
link
luckylion 1353 days 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.

link
snowwrestler 1354 days 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).

link