Possible to allow non-standard TLDs?

[InTheWoods]

Not all of my customers have standard public-facing TLDs that are accessible via the clearnet, as such, is there a way to permit non-standard TLDs? Is there a 'whitelist' of acceptable TLDs that DirectAdmin is checking when an account is created, or is there a way to disable or amend it that list to add several other TLDs?

---

Edit:

What's interesting is that it does allow some non-standard TLDs. For example, I can use .onion (Tor), .loki (LokiNet) and .ygg (Yggdrasil w/ Wyrd DNS) but I can't use .i2p (I2P network). I believe the number in the tld is what is causing the error, and not some sort of 'validity check' of the TLD itself.

Because we allow our customers to opt-in to have their clearnet site mirrored across various anonymity networks or host directly to them, it's important that they can use the TLD of their choice. Can we enable the ability to use a .i2p directly for those who wish to do that?

 

[factor]

i2p will let you build a domain on my server

domain.i2p
is this what you mean?

are you having issues when you click Create?

 

[InTheWoods]

Yeah. It's not that big of a deal, since I just assign each I2P site a dedicated IPv6 address and create a tunnel to it from an I2P router to make it resolveable over the I2P network as whatever.i2p, regardless if they enter whatever.com in the creation process. But it'd still be nice to be able to enter whatever.i2p natively.

The ability for this to work properly isn't overly dependent on them being able to enter whatever they want as a TLD, but may prevent some questions down the road from customers who may want to host an I2P only site and me having to explain that they can regardless of the TLD, yadda yadad