Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

.name Termination

neil.fraser.name

Post reply on HN
Print view View original

391–400 of 561 posts

Re: .name Termination

#391

Post by LelouBil »

cowsup wrote: post #332
plorg wrote: post #315

Earlier quoted context omitted.

I own a .name domain that is an initialism for my wife and I, and Namecheap never gave me any problems adding a record for vpn.mwai.name, for example. In fact I never even realized you could register a 3LD, much less that this was the intended(?) behavior.

The idea is: * .name is open for everybody * a company called "Global Name Registry" scooped up a BUNCH of common last names, including fraser.name * Global Name Registry then sold access to neil.fraser.name for far cheaper than the fraser.name domain would cost on its own; someone else could also buy john.fraser.name or jane.fraser.name, so the single fraser.name domain that they owned could have dozens of customers…

You should post it as a top level comment, I finally understood the situation exactly here.

Re: .name Termination

#392

Post by saimiam »

davkan wrote: post #263
bombcar wrote: post #230

Earlier quoted context omitted.

You can almost guess someone's age from that alone - they're more rare, but long domain names still appear that encode a city and a state, and you could just "grab" the first part when signing up.

Outside of the context of ccTLDs and city.state.gov etc, I struggle to think of examples 3LD+ domains where they are owned and operated by completely different concerns than the parent. If at some point you could just register your own mysite.state.gov domains willy nilly that's probably before my initial time online around 2000. Another poster raised the point of hosting services which is valid. But at present outsi…

All Indian banks use bankname.bank.in as their domain. I’m not sure who owns bank.in but this is a common suffix which is different from the .co.uk pattern.

Re: .name Termination

#393

Post by abofh »

palemoonsinking wrote: post #372
p4bl0 wrote: 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…

Because it's not worth it financially. After icann is the tld registrar, and after that above. So, if anyone is destroying it, it's not the registrar, it's the tld.

Re: .name Termination

#394

Post by noAnswer »

DaiPlusPlus wrote: post #341
koeliga wrote: post #272

Earlier quoted context omitted.

The risk of losing your big email account is higher than losing your domain. Furthermore, if you happen to lose your domain, it will in most cases be easier to recover than a restricted account.

> if you happen to lose your domain, it will in most cases be easier to recover than a restricted account. I used to think this, until I inadvertently let a registration fail to renew because I didn't update my expired credit-card's billing details with NameCheap - they did send me automated emails about it but I missed them, unfortunately. Their grace-period is only 30 days and I didn't notice the problem until 45 d…

The ratio between people who lost their "free big provider" account do to arbitrary algo decisions and people who lost their domain because they ignored provider's invoice for over a month must be 1.000.000 to 1. :-)

I use a prepaid provider. If at the day of the renewal there is no money "in the bank" they immediately release the domain. So yeah, I treat their reminders with priority. I really should change providers...

Re: .name Termination

#395

Post by bombcar »

davkan wrote: post #263
bombcar wrote: post #230

Earlier quoted context omitted.

You can almost guess someone's age from that alone - they're more rare, but long domain names still appear that encode a city and a state, and you could just "grab" the first part when signing up.

Outside of the context of ccTLDs and city.state.gov etc, I struggle to think of examples 3LD+ domains where they are owned and operated by completely different concerns than the parent. If at some point you could just register your own mysite.state.gov domains willy nilly that's probably before my initial time online around 2000. Another poster raised the point of hosting services which is valid. But at present outsi…

Many services today support vanity domains - Google even has special support for it: https://publicsuffix.org/list/public_suffix_list.dat

Re: .name Termination

#396

Post by Aachen »

KomoD wrote: post #156
Aachen wrote: post #129

Earlier quoted context omitted.

The post sounds like that wasn't possible; that this TLD operated by exception with third-level domains. It would be like asking why you don't just register smith.uk instead of smith.co.uk: because you can't ( https://en.wikipedia.org/wiki/.uk#Second-level_domains ) That's just my reading of the situation though. The person could now hope they're the first to claim their second-level domain once it becomes up for gra…

> It would be like asking why you don't just register smith.uk instead of smith.co.uk: because you can't You can. Anyone can register a .uk, and you don't need to own the .co.uk

Wikipedia says "second-level domains are managed by various government agencies, and generally more strongly controlled" besides the exceptions mentioned like co.uk. Why else would anyone ever have gone for a third-level domain?

If they've recently changed that and I'm misreading Wikipedia, that doesn't change the underlying point that the answer was "you couldn't". Otherwise I've grossly misunderstood the whole post and how verisign is proposing to cancel this person's third-level domain

Re: .name Termination

#397

Post by plorg »

cowsup wrote: post #332
plorg wrote: post #315

Earlier quoted context omitted.

I own a .name domain that is an initialism for my wife and I, and Namecheap never gave me any problems adding a record for vpn.mwai.name, for example. In fact I never even realized you could register a 3LD, much less that this was the intended(?) behavior.

The idea is: * .name is open for everybody * a company called "Global Name Registry" scooped up a BUNCH of common last names, including fraser.name * Global Name Registry then sold access to neil.fraser.name for far cheaper than the fraser.name domain would cost on its own; someone else could also buy john.fraser.name or jane.fraser.name, so the single fraser.name domain that they owned could have dozens of customers…

Is this quite accurate? My reading was that Global Name Registry was the registrar for the .name TLD, with Verisign providing DNS and email forwarding services, but that for several years GNR would only grant registration to third-level domains, then would set up corresponding second-level domains and email forwarding.

I guess in practice it doesn't make much of a difference for me anymore, I registered mwai.name 20 years after they began allowing second-level registrations and more than 15 years after GNR was sold to Verisign. So presumably GNR's concept was long-abandoned by the time I made my registration (which was, to be truthful, mostly based on mwai.name being the cheapest domain with the initialism). I was more curious about the implications of having held a second-level domain, whether it could have caused trouble for me or for a different person who held a tertiary domain. But also my registrar at least doesn't seem to allow tertiary domain registration for .name.

Any any case, nothing in OP or any of its referenced sources suggest Verisign is giving up .name. rather they will stop accepting and serving tertiary registrations, so if Neil wants to keep his domain he or another beneficent Fraser will need to register the fraser.name domain and register the subdomains for neil, joe, jill, or whichever other fraser currently owns a tertiary domain. The same would be the case for anyone else who still held a tertiary domain. Perhaps Verisign or the registrars who work with them might be able to migrate the registrations of anyone with these domains, particularly in what I suspect are most cases where there is a single tertiary registration under a secondary domain. Perhaps offer fraser.name to Neil and he can add his own subdomains.

I was intending to replying to a different comment on the above thread, sorry if this made my previous reply a bit incoherent.

Re: .name Termination

#398

Post by strken »

Glide wrote: post #362
dpoloncsak wrote: post #193

Earlier quoted context omitted.

I can say, as a SysAdmin, I have been taught and tell my users to check the domain to verify a website is real. It's a strange edgecase that the owner of John.Doe.com does not need to own Doe.com In every other case that I know about, to own the Joe subdomain of Doe.com, you would need to own Doe.com edit: I guess I've gotten so used to the government 3LDs I just don't even see them anymore, or just see something lik…

Looking at the threads below, very few people are discussing technical things in dns terms like zone or nameserver. Yeah. The way how most things on the internet prove ownership make the assumption that the 3ld is owned by the 2ld. Extend it once out for country specific ones and you cover most cases that people have to work with. Then when you consider DNS is fundamental infrastructure and people build secure things…

This doesn't seem like a problem if you exclusively support 3LDs and don't let anyone register 2LDs.

Re: .name Termination

#399

Post by xp84 »

strenholme wrote: post #289
xp84 wrote: post #250

Earlier quoted context omitted.

The auction plan is gross. It is unfair to say "This thing you thought you were buying the right to exclusively control (subject to continued renewal payments)? We're gonna transfer it next week to whichever Fraser pays us the most. Happy bidding!" It wouldn't be any more fair to do that than to announce to all .com owners that there will now be an auction between them and everyone who ever typed that name into a sea…

I agree. As a DNS implementer, the action plan is unnecessary. There are, what, only 22,000 or so .name domains. One can write code to do two lookups for firstname.lastname.name: If firstname.lastname.name is found, return the NS delegation. Otherwise, if lastname.name is found, return that NS delegation. Finally, if neither is found, return NXDOMAIN. One argument is that this is hard to implement in the real world (…

Love the practical explanation of how straightforward it should be. Especially with the finite set. Hell, they could send an email to all 22,000 saying "We're sorry, we have to raise your renewal fees by $12 a year. We hate to do this, but we're having to do a lot of extra work to support this unique type of domain." they'd bring in $264,000 a year, surely that should be enough to pay a single skilled developer to manage this and also be available to help smooth over any future complications.

Re: .name Termination

#400

Post by ACCount37 »

nanolith wrote: post #297

This risk factor is similar to one I brought up during architectural review of an IoT company I helped to build. It's why the identity certificates our devices used were entirely disconnected from domain names, and why the discovery protocol I put together did not rely on registered domains, but could use these as an untrusted part of discovery. Domain names are leased. Things that are leased can disappear. The compa…

"Online identity" seems like a castle built on quicksand in every single case.

What's your account tied to?

E-mail? That's usually on a mail server owned by someone else. If not, it's still on a domain owned by someone else.

Phone number? Definitely owned by someone else.

The only account that's reliably "yours" is one that asks for a login, a password, maybe a TOTP, and absolutely nothing else. Because everything else is introducing "things owned by a third party" into the equation.

Post reply on HN