Live data from Hacker News

.name Termination

neil.fraser.name

501–510 of 562 posts

Re: .name Termination

#501

Earlier quoted context omitted.

It seems insane because it seems like a big point was to have a permanent site for your name. This just devalues all domain names, showing that they can do a rug-pull at any time because they don't want to manage it (how about turn it over to a private company that can adjust costs so they can make a profit and keep it running?).

This is why new gTLDs are insane and stupid. It is about time there is some _yours for life_ DNS system. In this age, allowing domain names to be owned by other entities is almost like allowing a company business registration number or one's national id card number to be transferred to others. I think name squatting is a problem, but it is not like that current system has solved it.

DNS managed by the United Nations.

Re: .name Termination

#502

Earlier quoted context omitted.

Prior to reading the OP blog post, I had never looked into the particular rules that .name has. To me, prior to knowing how it works, I would have assumed that either a) john.doe.name would be a subdomain that someone who was just starting out had gotten for free supported by ads. Similar to having johndoe.freewebs.com back in the day. Not something most people would use for anything professional. or, b) doe.name was…

>I would not have guessed that .name 3LDs worked the way that it did if I hadn’t read about it. The situation in the OP is exactly what you just put as A)

The difference what I put as a) and what was written in the OP blog post are a couple of things.

1: In the blog post they wrote:

> this website vanishes in February. Despite the fact that it's registered and paid for until 2040.

So the way .name 3LDs worked, was that you had to pay for it. Not a free subdomain that’s handed out in return for the domain owner injecting ads into your site.

2: The other thing I meant by a) but that I failed to state explicitly is that in scenario a) I am imagining that doe.name and some other 2LDs with highly common last names had been bought by a third-party, similar to how the Freewebs company was owning freewebs.com and giving out subdomains of that to people. See also https://en.wikipedia.org/wiki/Webs_(web_hosting) for details on how Freewebs worked if interested and not familiar with them.

I would not have guessed that the .name registry itself was running a 3LD setup for everyone across all of .name, because it is so different from how all other TLD registries I know of manage the domain name hierarchies. For example .co.uk which is also 3LD was much more straightforward to understand and recognise historically because the 2nd level was a category (alongside a few other categories like .gov.uk, .ac.uk, .org.uk).

A few years ago, .uk opened to second level registration also, which somewhat similarly makes domains under .uk more confusing to me as someone outside the UK who knew about .co.uk and the likes because now I can no longer know if a 3LD under .uk is the way it is because it’s under an official category or not. For example, say that there is a 3LD domain manchester.autos.uk. I wouldn’t know if .autos.uk was an official category domain or not without specifically looking it up, now that 2LD registrations under .uk are open to others.

Re: .name Termination

#503

Earlier quoted context omitted.

> They're insane and should not be in charge. I remember back when we had to write mechanize scripts to drive a browser through the renewal process, because if you had dozens, hundreds, or thousands of domains there was no nonmanual way, especially if you wanted extended verification or something silly like that. So what I'm saying is, agreed and that has always been true.

That actually sounds like a good thing. Why are you hording hundreds or thousands of domains?

Really large companies have lots of domains even if they aren’t “hoarding” them. But even a few dozen domains is enough to need automation.

Re: .name Termination

#504
post #164

Earlier quoted context omitted.

A child born today sees email like we see the telegraph... they'll grumpily sign up to gmail just so they can get a verification email, and that'll be all it gets used for. Messaging their irl friends will be done in apps like Discord.

Truth. lol I ran a sizeable team around 2020 and I had to educate a couple of our new hires straight from college that they actually needed to check their work email, after they missed important HR related stuff and they had just completely not realized it was an avenue for company communication, with an assumption that everything was available on our heavily used slack.

They probably didn't realize why they needed multiple apps to communicate inside the company. I was in a situation where we had slack for communication between teams, email for corporate stuff similar you described, zoom for calls, personal messengers like WA for communicating with people in the company who didn't have slack, SMS/phone calls for alerts and various on-call staff. Total nonsense. No surprise I missed something.

Re: .name Termination

#505
post #273

Earlier quoted context omitted.

Another thing that should be obvious and yet they refuse to do: when there is a single third-level customer for a given second-level, offer them a way to get the second level domain. I've been asking VeriSign this for 15+ years, they always said no, even if at some point they confirmed that there were no other third-level than mine under that second-level domain. They're insane and should not be in charge.

Why would they want to drop the possibility of selling some as premium domains? If they have their shells setup right they will probably be able to get a premium from some 3rd level domain owners wrongly afraid someone else is interested. The main problem with the Internet today is that we didn't destroy ICANN when they started this TLD sell off crap. A replacement institution may have at least told Verisign a TLD th…

[dead]

Re: .name Termination

#506
post #328

Earlier quoted context omitted.

There should be a conflict resolution to gracefully degrade the third level to 2nd level when there is no competing name on the second level. But I didn't think about the 1st level competitors. There'd still need a mechanism to resolve that... 1. First come first serve? (e.g. whoever registered a y.name first, whether x is bob or sue is determined by the earliest registrant on record) 2. Lottery/random selection? 3.…

> There should be a conflict resolution to gracefully degrade the third level to 2nd level when there is no competing name on the second level. Yes. I've been asking VeriSign for this for years, and they always refused.

Update report: they are still categorically refusing, even for third-level customer who are alone (and have always been for 20 years) on the second-level they use. It makes no sense.

Re: .name Termination

#507

It kind of seems like an insane TLD structure to begin with, right? I always thought .co.uk was bad (you're just pinning yourself to whoever owns the .co. part, but at least browsers have some suffix list where you can't, I don't know, hijack some login cookie for all of .co.). Joe Smith and John Smith can independently register joe.smith.name and john.smith.name, do browsers have a wildcard suffix list for the 2nd l…

It definitely makes sense for stuff like (non-US) gov domains. Have a federal agency control the `gov.` domain and hand out subdomains to other agencies. See https://dachmarke.gov.de/ for example.

But I agree it makes no sense for public sales to the wider world such as `co.uk`. At least have the registrar be the govt company register and hand out subdomains to each registered company.

Re: .name Termination

#508

Earlier quoted context omitted.

What do you mean wildcard domain? Are you perhaps confusing domain renewals with dns entries?

Not OP, but I am guessing they have domains like fordcareers.com or fordsecurity.com instead of careers.fore.com or security.ford.com, etc

Exactly what they did in many instances.

Re: .name Termination

#509

Earlier quoted context omitted.

I was working for a company that had hundreds and thousands of domains. It was a fortune 50 company, and they had a policy generally against wildcard domains.

What do you mean wildcard domain? Are you perhaps confusing domain renewals with dns entries?

Instead of registering foo.com, and having bob.foo.com, they would register bobfoo.com - they had hundreds or thousands of certs, as a result, and had to renew them all annually or biannually. We didn't even manage all of the domains, we just had to renew the ones our group was responsible for, and it was in the dozens, and each form was ~30-40 actions to fill out correctly. I forget whether they were quarterly or we just ended up doing it all the time, but it was a maddening task.

Part of the explosion was that domains were not just in one TLD, they were bobfoo.com bobfoo.bar bobfoo.xyz and in many cases regionalized to bobfoo.co.uk or whatever. It wasn't "domain hoarding", because if you registered bobfoo.info you'd just get UDRP'd by corporate anyway, and nobody really wanted domains of the form somelongnamebobfoo.com

This was also before something like LetsEncrypt where you could automatically generate certs for programmatic usage, so they were all done manually.

Re: .name Termination

#510

Earlier quoted context omitted.

> Likewise, I've registered .lol and .fun domains but never would have assumed that just because they're available now, they will be available in perpetuity. Why wouldn't you assume this? > the standard way domain registration works is by choosing a single "second level" domain name, then adding subdomains The entire ccTLD systems of the UK, China, Germany, France, Japan, and many others would beg to differ.

> The entire ccTLD systems of the UK, China, Germany, France, Japan, and many others would beg to differ. .de doesn't use third level registrations.

Yes, you're right, thank you for the correction.
Post reply on HN