3 ms·

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 thin

by wormius 1mo ago

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. Bidding war? I think the problem is 2nd level domains who have the same name will be a problem when they find out all these other 3rd level are now expiring and can run a route to spoof? Likely wouldn't happen, but with the fuckery in the DNS that can happen... This is such a rash and weird decision to push through so quickly just because engineers find it "easier" while ignoring the implications of the move, seemingly when it comes to larger scale security. I assume there would have to be some method to prevent routing of third level domains to subdomains of two-levels... (or is that just me being a fool yet again, assuming we have competent administration of our systems).

deleted 1mo ago
[deleted]
mulmen 1mo ago
Or just honor the deal. The only reason for doing this is Verisign’s bottom line.
p4bl0 1mo ago
> 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.
- p4bl0 29d ago
  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.
  - glub 29d ago
    Maybe their justification is that allowing anyone to reserve means they'll have to admit they're screwing the ones with conflicts? Maybe there's some legal loophole that says screwing everyone == not screwing.
Nition 1mo ago
fraser.name does not seem to be currently registered, so it seems they could automatically give him that name, and hence solve the problem entirely. But I wonder if there might be some competing names on the third level? Like, he's neil.fraser.name, but what if there's also bob.fraser.name and they'd both very much like to keep their domains?
- marcus_holmes 1mo ago
  I think the point is that currently if anyone.fraser.name is registered, then fraser.name cannot be registered. The change that Verisign is making is to deregister all the *.fraser.name domain registrations, which will then free up fraser.name for registration. So it becomes a race to register fraser.name and the winner gets to recreate all the *.fraser.name subdomains they want, for whatever purpose they want.
  - Nition 29d ago
    I know, but what I mean is, if he's the only one that even owns anything at .fraser.name now, then it'd be easy to just automatically give him all of .fraser.name when that happens, and then he can recreate his subdomains without worrying about someone else snagging it first. But that doesn't work if someone else owns somethingelse.fraser.name, because you can't give it to both of them.
ctippett 29d ago
New Zealand did this when they introduced/allowed .nz registrations[1]. If you had a domain under .co.nz, .net.nz, etc, you were reserved the right to register the same name under the new TLD. If two different registrants shared the same name, a conflict resolution was put in place to adjudicate who would be allowed to register the .nz equivalent of their domain. I had/have a .net.nz and someone else owned the .co.nz. I went through the conflict resolution process and ended up being able to register the .nz. Not sure if or how other registrars manage this sort of thing, but I thought the way NZ's Domain Name Commission handled things was pretty fair and transparent. [1] https://dnc.org.nz/tools-and-services/how-do-i-2/register-a-conflicted-domain-name/ https://dnc.org.nz/tools-and-services/how-do-i-2/register-a-...

by wormius 1mo ago

deleted 1mo ago

[deleted]

mulmen 1mo ago

Or just honor the deal. The only reason for doing this is Verisign’s bottom line.

p4bl0 1mo ago

> 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.

p4bl0 29d ago
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.
- glub 29d ago
  Maybe their justification is that allowing anyone to reserve means they'll have to admit they're screwing the ones with conflicts? Maybe there's some legal loophole that says screwing everyone == not screwing.

Nition 1mo ago

fraser.name does not seem to be currently registered, so it seems they could automatically give him that name, and hence solve the problem entirely. But I wonder if there might be some competing names on the third level? Like, he's neil.fraser.name, but what if there's also bob.fraser.name and they'd both very much like to keep their domains?

marcus_holmes 1mo ago
I think the point is that currently if anyone.fraser.name is registered, then fraser.name cannot be registered. The change that Verisign is making is to deregister all the *.fraser.name domain registrations, which will then free up fraser.name for registration. So it becomes a race to register fraser.name and the winner gets to recreate all the *.fraser.name subdomains they want, for whatever purpose they want.
- Nition 29d ago
  I know, but what I mean is, if he's the only one that even owns anything at .fraser.name now, then it'd be easy to just automatically give him all of .fraser.name when that happens, and then he can recreate his subdomains without worrying about someone else snagging it first. But that doesn't work if someone else owns somethingelse.fraser.name, because you can't give it to both of them.

ctippett 29d ago

New Zealand did this when they introduced/allowed .nz registrations[1]. If you had a domain under .co.nz, .net.nz, etc, you were reserved the right to register the same name under the new TLD. If two different registrants shared the same name, a conflict resolution was put in place to adjudicate who would be allowed to register the .nz equivalent of their domain. I had/have a .net.nz and someone else owned the .co.nz. I went through the conflict resolution process and ended up being able to register the .nz. Not sure if or how other registrars manage this sort of thing, but I thought the way NZ's Domain Name Commission handled things was pretty fair and transparent. [1] https://dnc.org.nz/tools-and-services/how-do-i-2/register-a-conflicted-domain-name/ https://dnc.org.nz/tools-and-services/how-do-i-2/register-a-...