TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Ask HN: List of Subdomains to Reserve

9 点作者 ILIWYCMBgPicCha大约 1 年前
One of the features I am working on for my app (https:&#x2F;&#x2F;bigpicture.site) is the ability for each customer to have a custom subdomain in their url (similar to slack where each workspace is in the form of {name}.slack.com.)<p>I understand the technical details of setting up the wildcard subdomains and handling it, but I am curious if there is a canonical list somewhere of subdomains I shouldn&#x27;t let a customer register.<p>For instance, I wouldn&#x27;t want a customer to use www as their workspace name. www.bigpicture.site should be reserved.<p>What other subdomain names should be reserved? Just from brain storming, here is the list I came up with. But I&#x27;d love to know if there is a better list somewhere:<p>www mail ftp web smtp imap pop pop3 blog support about social billing admin knowledge help community<p>Additionally, I am going to reserve anything that starts with the letters &quot;bp&quot; so I can use those internally.

6 条评论

jasonjayr大约 1 年前
You may be safer by keeping customer stuff on a subdomain of your primary domain, or even having a user content domain.<p>Otherwise you will be chasing this for a long time:<p>Official.example.net, postmaster.example.net, search.example.net, mail.example.net, payments.example.net<p>Vs<p>Official.users.example.net, mail.users.example.net, etc.<p>You may want to consider connecting with the PSL:<p><a href="https:&#x2F;&#x2F;en.m.wikipedia.org&#x2F;wiki&#x2F;Public_Suffix_List" rel="nofollow">https:&#x2F;&#x2F;en.m.wikipedia.org&#x2F;wiki&#x2F;Public_Suffix_List</a>
评论 #39593060 未加载
KomoD大约 1 年前
&gt; But I&#x27;d love to know if there is a better list somewhere<p>There&#x27;s a few lists but I suggest going through them and removing some entries.<p>Here&#x27;s one list (tons of entries that don&#x27;t make much sense): <a href="https:&#x2F;&#x2F;github.com&#x2F;jedireza&#x2F;reserved-subdomains&#x2F;blob&#x2F;master&#x2F;names.json">https:&#x2F;&#x2F;github.com&#x2F;jedireza&#x2F;reserved-subdomains&#x2F;blob&#x2F;master&#x2F;...</a><p>This is another list which is a bit better quality: <a href="https:&#x2F;&#x2F;minhajuddin.com&#x2F;2016&#x2F;03&#x2F;09&#x2F;subdomains-to-restrict-from-your-saas-app&#x2F;" rel="nofollow">https:&#x2F;&#x2F;minhajuddin.com&#x2F;2016&#x2F;03&#x2F;09&#x2F;subdomains-to-restrict-fr...</a><p>Another list (there&#x27;s some I don&#x27;t agree with): <a href="https:&#x2F;&#x2F;github.com&#x2F;nkkollaw&#x2F;reserved-subdomains&#x2F;blob&#x2F;master&#x2F;reserved-subdomains.yaml">https:&#x2F;&#x2F;github.com&#x2F;nkkollaw&#x2F;reserved-subdomains&#x2F;blob&#x2F;master&#x2F;...</a>
评论 #39601073 未加载
ipaddr大约 1 年前
Some ideas Don&#x27;t let them select a name. - Create a random url ghrff.domain.com<p>Don&#x27;t do this on your primary domain buy a new one<p>If you still want to go ahead and you&#x27;ve created an &#x27;a&#x27; record for www or mail previously your a record will superseed the wildcat entry which will create a bug where the user cannot access their subdomain. You need to filter any a records you&#x27;ve created to avoid this.
pbowyer大约 1 年前
It&#x27;s important to think about reputational risk when coming up with the list. You probably don&#x27;t want swear words in front of your domain.
评论 #39601066 未加载
DamonHD大约 1 年前
I would also suggest at least initially anything which is not pure ASCII alphanumerics, eg starting with _ since those may be special for say DMARC.
swman大约 1 年前
What are the DNS implications?