返回首页

对比阅读

对比阅读:Old Domain Died Overnight: A 30-Minute Migration Check 与 旧域名突然不能用了:给个人站做一次迁移体检

AEN
.name 域名个人网站自由职业者·

Old Domain Died Overnight: A 30-Minute Migration Check

11 p.m. Last night, I nearly handed over the wrong site

Last Thursday at 11 p.m., I was in Hangzhou updating a personal website for a freelance photographer. The domain was bought, the pages were ready, and I almost broke the way an existing client reached the site. An address that had always worked suddenly failed, leaving anyone who shared it on a blank page. I got stuck here too: I focused on whether the new pages looked good and never checked whether the old address would still work.

This time, the issue was a change to the grandfathering rules for .name domains. The website technology was fine, but some long-standing legacy domains may need to migrate under the new registration and renewal rules. Neil Fraser documented the change on his personal blog, and developers have discussed in the community which legacy domains are affected. This was not “the site must be rebuilt.” It was more like checking an address book: which links stay, which move, and whether the old address will work again afterward.

Today, reproducing this check costs 0 yuan and takes about 30 minutes. The technical barrier is not high, but I need to understand the domain status shown on the registrar’s page. First, I log in where I bought the domain and find “Domain List” or “Manage.” I do not rush to renew. Instead, I record every legacy address still in use, then search for “.name domain migration” or “domain retention rules.” If I use a forwarding service such as Cloudflare, I also check the redirects for the old addresses. If the site still works, I leave things alone for now instead of changing them randomly.

When I am just starting with one personal homepage, I spend 10 minutes listing every link I have shared publicly and delay migration. When I already have one or two clients, I test the old links one by one against the client list and preserve the existing redirects. When I am scaling and have several sites or subdomains, I ask a technical helper to build a complete inventory before choosing a coordinated migration. The mistake I am most likely to make is testing only the homepage on my computer, not the old link a client has kept in WeChat for three years.

BZH
.name 域名个人网站自由职业者·

旧域名突然不能用了:给个人站做一次迁移体检

昨晚十一点,我差点把客户官网交出去

上周四晚上十一点,我在杭州给一个自由摄影师改个人网站,域名已经买好、页面也摆好了,却差点把旧客户原来的访问方式弄丢。以前能打开的地址突然失效,客户一转发就落到空白页。我也卡过:当时只顾着看新页面好不好看,没先确认旧地址能不能继续用。

这次碰到的是“.name”域名的历史兼容规则变化。简单说,网站技术没坏,但有些沿用多年的旧域名在新的注册与续费规则下可能需要迁移。Neil Fraser 把这条变化记在个人博客里;开发者社区里也有人讨论哪些旧域名会受影响。它不是“页面必须重做”,更像给地址本做一次核对:哪些还留、哪些要搬、搬完能不能回到旧地址。

今天想复刻这份排查,成本是 0 元、约 30 分钟;技术门槛不算高,但要看懂注册商页面里的域名状态。第一步先登录你买域名的地方,找到“域名列表”或“管理”,不要急着点续费,把正在使用的旧地址逐一记下来,再搜索“.name 域名迁移”或“域名保留规则”。如果你用 Cloudflare 这类转发服务,还要额外确认旧地址的跳转设置;现在不查也没事,网站仍能访问就先别乱改。

如果你刚起步、只有一个个人主页,我会先花 10 分钟列出所有对外发过的链接,暂时不迁;如果你已有 1-2 个客户,我会按客户名单逐个测试旧链接,并保留原来的跳转;如果你正在扩规模、站点和子域名较多,我会让技术帮手做一次完整清单,再决定集中迁移。我们最容易犯的错,是只测电脑上的首页,没测客户微信里存了三年的旧链接。