Rendered at 10:23:46 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
kiesel 1 hours ago [-]
Worth noting, this doesn't affect domain.name, thus 2nd level domains. I was actually unaware you could directly register a 3rd level domain... Got my .name in the sunrise phase of .name, though it later rendered obsolete by name change on marriage (but still got it).
pelagicAustral 52 minutes ago [-]
Biggest rug pull in the history of dns
InsidiousWombat 5 minutes ago [-]
Nah, turning existing domains premium (sometimes 10x or higher cost) under the users is IMO worse, as it can catch people that just have it on auto-renew unaware.
wodenokoto 19 minutes ago [-]
Wait, so if you own Johnson.name you and use John.Johnson.name as your web address, that will stop working?
OJFord 2 minutes ago [-]
No this is people who have registered john.johnson.name, but johnson.name remains Verisign's (and e.g. unrelated Alice has also registered alice.johnson.name)
OtomotO 17 minutes ago [-]
I don't think so. If you own it, you can have any subdomain.
At least I hope this is the case. I have a memorial page for my uncle under hisfirstname.ourlastname.name
> His registrar informed him that his registration will be terminated in February (even though it’s paid through 2040).
Wonder if registrars will refund to people's cards.
victorbjorklund 26 minutes ago [-]
Unrelated. What happened with .io? Didn’t they say they would disappear or did that change?
Symbiote 23 minutes ago [-]
The proposed treaty between Britain and Mauritius was conditional on the approval of the USA (due to the UK/US air base), and that approval wasn't given.
By kicking old nerds off legacy.domain.name, they can relist domain.name on the open market and make an absolute killing.
toomuchtodo 3 days ago [-]
Consider editing title to be "Tell HN:" Thank you for the PSA!
nikanj 3 days ago [-]
Good point, changed. Thanks!
mnd999 1 hours ago [-]
I have a second level and I’m in the process too. This kind of shitty behaviour warrants bankruptcy.
moron4hire 44 minutes ago [-]
Jesus Christ. In 25 years of working on the Web, this is the first time I'm hearing of "third level domains". WTF? Where and when did this come from?
No shade to the folks being harmed by this situation. Sorry. I'm just really non-plussed at the idea that the registrar is charging for what looks like should be a DNS prefix.
jeroenhd 14 minutes ago [-]
.name has been doing this for 25 years so I guess you must've missed them right when you got started!
For .uk, this scheme was the default until 2014 (a long time, considering it's first use was in 1985). Everything was .co.uk or .org.uk and you bought those directly with registrars. Then, in 2014, .uk registrations were allowed, and the .co.uk and .uk domains now coexist.
edent 41 minutes ago [-]
You've never seen example.co.uk? Many countries use them because the top level domains for gov, edu, etc are restricted to one country.
dspillett 19 minutes ago [-]
Those are not quite the same though, being something specific and short so essentially behave like a tld in their own right. For a long time you couldn't buy a <something>.uk, it had to be .co.uk or similar, so those _were_ the tld.
The way .name worked you could directly register <name1>.<name2>.name instead if getting <name2>.name and setting up <name1> as a subdomain. It meant john.smith.name and dave.smith.name could be completely separate registrations. You can't generally register <name1>.<name2>.tld like that.
Symbiote 17 minutes ago [-]
There's two on the second page of active HN discussions, telegraph.co.uk and independent.co.uk.
Should we mention fourth-level domains, like ci.east-palo-alto.ca.us or stanborough.herts.sch.uk?
TZubiri 22 minutes ago [-]
there’s nothing special about any level of domains, it was always a hierarchical protocol
jeroenhd 6 minutes ago [-]
The difference is that .name allowed you to buy steven.smith.name and someone else could buy john.smith.name. The shared hierarchy between those names is the .name domain, .smith.name doesn't really exist.
Of course, this could be trivially fixed if .name would take the shared part of every second level domain, treated it like a TLD for legacy customers, and turn it into a hierarchical system.
But they'd need to do that for possibly thousands of paying customers, there's no way they'd be able to afford that, Verisign only makes 1770000000 dollars of yearly revenue! Honoring these existing contracts would bankrupt them!
At least I hope this is the case. I have a memorial page for my uncle under hisfirstname.ourlastname.name
Wonder if registrars will refund to people's cards.
https://en.wikipedia.org/wiki/British_Indian_Ocean_Territory
No shade to the folks being harmed by this situation. Sorry. I'm just really non-plussed at the idea that the registrar is charging for what looks like should be a DNS prefix.
For .uk, this scheme was the default until 2014 (a long time, considering it's first use was in 1985). Everything was .co.uk or .org.uk and you bought those directly with registrars. Then, in 2014, .uk registrations were allowed, and the .co.uk and .uk domains now coexist.
The way .name worked you could directly register <name1>.<name2>.name instead if getting <name2>.name and setting up <name1> as a subdomain. It meant john.smith.name and dave.smith.name could be completely separate registrations. You can't generally register <name1>.<name2>.tld like that.
Should we mention fourth-level domains, like ci.east-palo-alto.ca.us or stanborough.herts.sch.uk?
Of course, this could be trivially fixed if .name would take the shared part of every second level domain, treated it like a TLD for legacy customers, and turn it into a hierarchical system.
But they'd need to do that for possibly thousands of paying customers, there's no way they'd be able to afford that, Verisign only makes 1770000000 dollars of yearly revenue! Honoring these existing contracts would bankrupt them!