← Back to context

Comment by xp84

14 hours ago

Even that doesn't pass basic scrutiny. The same ambiguity can and always will exist with tim-apple.com and tim.apple.com - there's nothing here that needs fixing.

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 like .co.uk or .edu.us as a TLD by itself, but yeah those exist too. Still the exception to the rule

  • That is definitely not true. There are literally thousands if not tens of thousands of well known domains that do this. .co.uk is a very common example.

    • .name is still a weird edge case because of the naming rules. Whether or not all subdomains under doe.name belong to the same person depends solely on whether the first person registered "doe.name" (in which case they do) or "john.doe.name" (in which case they don't, and "doe.name" is excluded from purchase as a standalone domain).

      1 reply →

    • I think the problem is that .co.uk, .gov.uk and so on are very well known in the UK.

      The .name subdomain rules are not very well known anywhere.

      1 reply →

    • The fact that multiple organizations need to keep a public list of known 3LDs proves it's the edge case, does it not?

      "Here's a list of things that look like subdomains for you to treat as 3LDs instead of subdomains" sounds exactly like the solution to an edge case to me.

    • This seems largely country dependent with some exceptions.

      In the US, once upon a time, elementary/middle/highschools might be attached to something like schoolname.district.state.gov. But now, even my local area school now has a .com. It seems that older hierarchy style is falling out of fashion for smaller/shorter domains across public services, schools, government agencies, etc.

      Now here it seems to be either a .com, .gov, .org, or a totally different and newer tld. Even .net has fallen out of fashion.

      2 replies →

  • 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 on top of it, (ahem DNS challenges for certs), it's remarkable that anyone would want or desire edge cases.

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

  • Yet that is a problem the owner of such a domain has freely entered into by buying that domain, it's their right to keep it despite this apparent problem, if they wish.

    • Understood, and .name isn't being used enough in business to worry about 'the effect it will have on my users'. Just pointing out that it doesn't work like the 'norm' (although I guess it's not quite as unique as I thought, either)

  • Hello sysadmin. Good luck navigating the internet.

    What you should know, and what your browser does know and automatically applies cookie policy and colouring your URL bar, is the Public Suffix List: https://en.wikipedia.org/wiki/Public_Suffix_List

    It will let you know that, for example, one does not need to own .co.uk to own the subdomain foo.co.uk.

True, they can’t outright prevent the ambiguity, but much fewer people will go to the trouble of establishing such subdomains when the option isn’t directly offered by the registrar.

This is my theory because, a priori, 3LDs should be more profitable than 2LDs, because with 3LDs John Doe and Jane Doe don’t have to compete over doe.name, but instead can each separately purchase john.doe.name and jane.doe.name. Apparently, however, that’s not a benefit of 3LDs in practice, which leads me to conclude that john-doe.name and jane-doe.name just sell better.

  • 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 registered by one of the people in a family of Doe’s where every Doe is pretty closely related. For example, John of john.doe.name and Jane of jane.doe.name are husband and wife, or third cousins, or what have you. Most of the content, I would assume, is mostly about things that relate to the family. Like maybe one guy is doing a family genealogy project tracing the roots of this little cluster of Doe’s back in time and has made a site covering the findings from his research. And another one probably has some photo albums with pictures of like previous Thanksgivings and other family get togethers. In other words, nothing I would care about unless I was in their family or a very close friend of the family.

    I would not have guessed that .name 3LDs worked the way that it did if I hadn’t read about it.

    And on the other hand, if I saw just www.doe.name or johndoe.name, I would not make such assumptions. It would be not much different than seeing www.doe.com or johndoe.com respectively. I would just assume that .com was already taken and therefore they used .name, or that they happened to like the .name TLD because it emphasises that their site has their name as domain name.

  • > This is my theory because, a priori, 3LDs should be more profitable than 2LDs,

    3LDs are less valuable. In a market of many different tlds, why register foo.bar.name when you could get foobar.name or foobar.something_else