Skip to content

How should we handle the 2LDs of the .name TLD? #2306

@wdhdev

Description

@wdhdev

I have gained access to the full zone file of the .name TLD through ICANN's CZDS (https://czds.icann.org), with the intention of adding the 2LDs to the PSL.

The .name TLD has a bunch of 2LDs, which as far as I know allow registration. An example of one is harrison.name, it has no delegated NS records, however it has MX records in the root zone, which is how the .name registry operates these 2LDs. So someone cannot directly register an already created 2LD like harrison.name, however they can register at the 3rd level (e.g. william.harrison.name).

I'm not 100% sure how they determine what to configure as a 2LD or not, or whether they just delegate any domain at the 2nd level at request. (This is a possibility because there are a lot of reserved 2LDs that only have one 3rd level domain.)

Should we maybe sort this data in a way so we only add 2LDs that have say 10 or more subdomains at the 3rd level? The reason I say this is because there are around ~15,500 2LDs when using a basic search program.

Metadata

Metadata

Assignees

No one assigned

    Labels

    🚩ICANN (IANA/ICP-3) SectionPR changes in the ICANN/IANA section typically reserved for TLDs.

    Type

    No type

    Projects

    Status

    Done or Won't

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions