51 points nikanj 2 days ago 27 comments
Personally, I'm stuck in Microsoft hell because Azure admin emails cannot be changed and support is both uncaring and powerless.
nikanj 2 days ago | parent
jolmg 2 hours ago | parent
Wonder if registrars will refund to people's cards.
kiesel 2 hours ago | parent
mnd999 2 hours ago | parent
moron4hire 1 hour ago | parent
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.
edent 1 hour ago | parent
dspillett 1 hour ago | parent
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.
moron4hire 44 minutes ago | parent
Though, from a certain academic perspective, I can maybe see some idiot making an ignorantly in-good-faith argument for something like personal names needing to be controlled at the registrar level. Never mind that all of the registrars are evil or that most people share a name with someone else in the world. It ironically goes hand-in-hand with their evilness that they should have the power to deny one party the use of their own name due to the incidental, unrelated, but preemptive use of that name by another party.
Said as the top search result for my firstname-lastname amongst at least 7 such people that I'm aware of, one of which I know is also a software developer. I only continue to preemptively register accounts under my one and only true name to avoid receiving their false and deceitful spam when they forget their email domain is Yahoo, not Gmail...
I know, you might be thinking he's are doing it on purpose to punish me for being more popular. I could see that if the email I was getting was porn or scams or whatever. It's not. It's mortgage paperwork. It's personalized cake decorations. It's hotel reservations. This dude is the worst at maintaining his data I've never met.
Symbiote 1 hour ago | parent
Should we mention fourth-level domains, like ci.east-palo-alto.ca.us or stanborough.herts.sch.uk?
TZubiri 1 hour ago | parent
jeroenhd 54 minutes ago | parent
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!
singpolyma3 7 minutes ago | parent
jeroenhd 1 hour ago | parent
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.
victorbjorklund 1 hour ago | parent
Symbiote 1 hour ago | parent
https://en.wikipedia.org/wiki/British_Indian_Ocean_Territory
swiftcoder 22 minutes ago | parent
wodenokoto 1 hour ago | parent
OtomotO 1 hour ago | parent
At least I hope this is the case. I have a memorial page for my uncle under hisfirstname.ourlastname.name
OJFord 50 minutes ago | parent
OtomotO 20 minutes ago | parent
I have subdomains like {myfirstname}.{lastname}.name ... {lastname}.name is mine
So obviously {myfirstname}.{lastname}.name is a subdomain...
Could someone now have bought {myfirstname}.{lastname}.name and DNS would go to their page?
If so, I find the new behaviour way more sane...
If I wanted to sell a subdomain, I could do this, no questions asked. I just point the subdomain to another IP.
But I pay for {lastname}.name so it should be mine, just like any other .tld I have!