Hacker News new | ask | show | jobs
by jasonjayr 844 days ago
You may be safer by keeping customer stuff on a subdomain of your primary domain, or even having a user content domain.

Otherwise you will be chasing this for a long time:

Official.example.net, postmaster.example.net, search.example.net, mail.example.net, payments.example.net

Vs

Official.users.example.net, mail.users.example.net, etc.

You may want to consider connecting with the PSL:

https://en.m.wikipedia.org/wiki/Public_Suffix_List

1 comments

> or even having a user content domain.

This is the way to go, spend another ~$10/yr and keep customer subdomains on another domain.

Another option instead of doing "dave123.users.example.net" is to suffix or prefix the subdomain with something, like "zone-dave123.example.net".

Yeah, using a different domain isn't a bad idea. I had considered it, but I know slack doesn't do it. (I also know I'm not Slack).

There was a service I used some years (decades?) ago that let users choose from three or four domains that they owned. I could always do that in the future, too.