discuss .O Discussion

[Armageddon]

Managed by independent members of the community OpenNIC
Any opinion
Right now are for reg. at Epik.com
I don't know if other registrar ofer for registration .O
Notice also already few of them sold on Namepros
Any idea how to be setup on/for VPN to add content ?
Personal i reg. few among them: Mexic.o, Tatto.o , Cong.o , Audi.o , Radi.o , SanFrancisc.o &
Toky.o - for 2021
Show here your registration & your opinion or any info

Kind regards,
Ovi

 

[Arjun Oli]

Can't say. The world is changing. Who knows, this can be the next thing. It only takes a significant number of users supporting the system.

Yes, who knows, It is very cheap, just buy and keep.

 

[private123]

@Shdwdrgn
First confusion clear; minimum digit .geek domain registration allowed ?

.geek domain names must be at least 3 characters long (before the .geek) and be otherwise consistent with the relevant RFC's.
https://wiki.opennic.org/opennic/dot/geek

Epik provided single digit .geek domain
Example. z.geek

 

[web3dev]

.

When new TLDs are suggested, we do our research to make sure it's not something ICANN is considering or that another alt-root is already using. There was also mention of the fact that reg.for.free no longer resolves for registering OpenNIC domains -- which is because ICANN started using .free and we had to shut down ours. The .libre TLD was formed and all existing domains were moved to that one, again to avoid conflicts with the ICANN root zone. (The domain be.libre has taken the place of reg.for.free.) We do our best to ensure that our DNS servers always return legitimate information and follow the expected standards.

Appreciate this self imposed ethics.

 

[Paul]

@Shdwdrgn
First confusion clear; minimum digit .geek domain registration allowed ?

.geek domain names must be at least 3 characters long (before the .geek) and be otherwise consistent with the relevant RFC's.
https://wiki.opennic.org/opennic/dot/geek

Epik provided single digit .geek domain
Example. z.geek

Epik's .geek and OpenNIC's .geek aren't the same. example.geek at Epik and example.geek at OpenNIC could be owned and controlled by two separate people.

 

[Rob Monster]

Epik's .geek and OpenNIC's .geek aren't the same. example.geek at Epik and example.geek at OpenNIC could be owned and controlled by two separate people.

As a courtesy to OpenNIC, we suspended selling overlapping TLDs. There is an abundance of namespace for Alt TLDs. @Sufyan Alani will be in touch with them to explore API integration.

 

[web3dev]

As a courtesy to OpenNIC, we suspended selling overlapping TLDs. There is an abundance of namespace for Alt TLDs. @Sufyan Alani will be in touch with them to explore API integration.

Appreciate the gesture.

 

[DaveX]

Epik's .geek and OpenNIC's .geek aren't the same. example.geek at Epik and example.geek at OpenNIC could be owned and controlled by two separate people.

so it would depend on which dns server ip?

 

[DaveX]

As a courtesy to OpenNIC, we suspended selling overlapping TLDs. There is an abundance of namespace for Alt TLDs. @Sufyan Alani will be in touch with them to explore API integration.

Are .o and .geek at Epic now suspended? What about names already registered?

 

[dirk]

Hi folks, I wanted to jump in and clear up some misconceptions about OpenNIC that I've been reading in this thread. If you have any further questions, feel free to ask!

First off, to reiterate what has already been stated, domains from OpenNIC are NOT the same as domains from Epik. While we have had many discussions over the years about running OpenNIC more like a business it always falters because we will not charge for our domains (and as was already mentioned, alt-root domains have exactly zero monetary value and we aim to keep it that way). In general, OpenNIC has always been a learning project, where people come to understand the nuts&bolts of what makes the internet function. It gives everyone a chance to see how the various levels of DNS zones interoperate. More recently we have also gained a following of members who connect under ISPs with intentionally-broken DNS services that do not properly reply with NXDOMAIN or other errors (generally because the ISP uses mis-typed domains for their own monetary gain).

Using an alt-root does not require any sort of plugins or other software installations. You simply enter a couple of our DNS server IPs into your network setup and you are done. There may be some browser plugins available that let you access alt-roots without modifying your network setup, but that seems like the more difficult way to achieve the goal.

I've been with OpenNIC since 2002, and I think maybe I remember the issue with the .biz TLD conflicting with ICANN? That's ancient history though, and as a rule we now try to make sure we never have conflicting domains. When new TLDs are suggested, we do our research to make sure it's not something ICANN is considering or that another alt-root is already using. There was also mention of the fact that reg.for.free no longer resolves for registering OpenNIC domains -- which is because ICANN started using .free and we had to shut down ours. The .libre TLD was formed and all existing domains were moved to that one, again to avoid conflicts with the ICANN root zone. (The domain be.libre has taken the place of reg.for.free.) We do our best to ensure that our DNS servers always return legitimate information and follow the expected standards.

Another comment suggested that OpenNIC zones are not decentralized. We currently have 76 public DNS servers in 22 countries, all of which can resolve any of our TLDs and domains, and which also have pointers to the DNS servers of other alt-roots we peer with. Yes it is true that registrations are typically handled by individual servers, but in the case of the .o zone which is being discussed that registration takes place through github.

If anyone has an interest in the OpenNIC project, please see our website at opennic.org.

Thank you for taking the time to set up an account and answer some questions! I appreciate it!

 

[Shdwdrgn]

@Shdwdrgn
First confusion clear; minimum digit .geek domain registration allowed ?

.geek domain names must be at least 3 characters long (before the .geek) and be otherwise consistent with the relevant RFC's.

Epik provided single digit .geek domain
Example. z.geek

Yes, opennic's .geek zone requires a minimum of three characters for domain names. That was in response to a number of people trying to register a bunch of 1- and 2-digit domain names, then complaining that they weren't able to resell the domains which they got for free.

 

[Steven McEvoy]

Yes but what if there is a world war or corporate internet takeover? Or an alien space war?

No one will be able to access the name unless they have access to your server... The hole thing is worthless

 

[Rob Monster]

Are .o and .geek at Epic now suspended? What about names already registered?

We are resolving them as before and will explore a formal cooperation with OpenNIC on fast-track.

The big win for them is that we can deploy OpenNIC TLDs on what may end up being millions of Toki servers. When folks see what Toki does, I think they will be impressed.

Among other things, Toki serves as a resilient, decentralized authoritative DNS resolver for domains that people could own forever.

Obviously I expect a peaceful coexistence with ICANN and ccTLD, but initiatives like OpenNIC have their place. They just need better distribution.

 

[Steven McEvoy]

No one will be able to access the name unless they have access to your server... The hole thing is worthless

@Rob Monster I see you disagree, Please explain to me that their is a way I can type in an alt domain extension in the browser right now and go to the website?

 

[Shdwdrgn]

so it would depend on which dns server ip?

That is correct. If you point your DNS to an OpenNIC server, you get OpenNIC's zone of .geek domains. If you point your DNS to an Epik server, then you get Epik's zone of .geek domains.

This is the whole reason that domains have value to begin with. DNS can only use a single root zone, and most of the world points to an ICANN root. This flaw creates an artificial scarcity with domain names, but as you can see from the OpenNIC project literally anyone can set up a root zone and create new TLDs with minimal cost (all of the software is free, we only pay for the electricity to run our servers).

 

[Shdwdrgn]

Among other things, Toki serves as a resilient, decentralized authoritative DNS resolver for domains that people could own forever.

Rob, I wanted to point out that OpenNIC has had bad experience with decentralized resolvers in the past -- specifically the .bit zone. The issue here was that there was no controlling agency that required strict confirmation of real persons registering the domains. This led to hundreds of domains being used to spread malware, entities such as Spamhaus trying to clamp down on the spread, and OpenNIC being caught in the middle. In the end we could find no way to solve the various problems without compromising our own values, so our members voted to drop peering with the .bit zone.

 

[web3dev]

Okay, registered 123.geek from be.libre
Seems need to renew every month.
Will try to create something there.
@Shdwdrgn hope you staying with us enriching about alt domains and OpenNIC. Why not create an official OpenNIC thread?

 

[Shdwdrgn]

Okay, registered 123.geek from be.libre
Seems need to renew every month.
Will try to create something there.
@Shdwdrgn hope you staying with us enriching about alt domains and OpenNIC. Why not create an official OpenNIC thread?

I just found out about this board yesterday, and with the flurry of activity I haven't had time to do anything beyond write some responses. I'll see about starting a new thread once I have more time.

The 1-month requirement and limitations on the number of domains that can be registered at once is there to weed out the numerous people who learn about OpenNIC, register a lot of domains, and never come back. You'll probably get another email in the next few days letting you know that your domain will expire soon, at which point you can renew it for a full year.

 

[Rob Monster]

@Shdwdrgn

With all due respect, OpenNIC looks like an academic project. Here is where we can agree, one way or another, Internet 2.0 is coming.

Here is what Epik has assembled:

- Registry platform capable of supporting any TLD
- World class and award-winning Registrar platform
- Domain Marketplaces (NameLiquidate and Epik)
- Content Delivery Network (BitMitigate)
- Denial of Service Mitigation (BitMitigate)
- Autonomous System (AS34962)
- IPv4 / IPv6 ranges as RIPE member
- Intermediate Root Certificate Authority (DNEncrypt)
- Anycast DNS
- VPN wit post-quantum encryption (Anonymize)


In addition:

- High availability Kubernetes hosting (CloudChase)
- Decentralized and ultra low cost Toki servers running on Raspberry Pi 4 devices (coming this month)

You can follow some of our other projects here:

https://www.epik.com/about/labs/

Our Alt TLDs are here:

https://registrar.epik.com/prices/registration/alt

For next TLDs introduced, we'll plan an orderly sunrise process that favors existing registrants of .com, .net, and .org, in that order, and with an emphasis on FOREVER domains, a topic I discussed here.

To avoid confusion, we'll try not to trip over OpenNIC TLDs. No promises there.

The names that we did register will continue to resolve across our network. We reserve the right to re-open those name spaces at a time of our choosing.

Best of luck to you.

 

[Big Mac]

Hello everyone. How are you? I think these "Alt TLDs" may present true internet land ownership. The idea that you or I can possibly own a TLD is something that eveyone needs to really take a hard look at.

So, I did my little test to see if these alternative TLDs can possibly work. First, I opened up my chrome browser and added the "Blockchain DNS" extension. Then I proceeded to https://members.opennicproject.org/ to sign up as a new user. I signed up and was sent a confirmation link in my email. Clicked on the link in my email and I was confirmed. Next, I went to http://be.libre/ and signed in with my OpenNic username and password to register a free .Geek domain name. I registered 888.geek (it was available), set the nameservers to my webhosting company of choice, and probably had to wait less than 24 hours for the nameservers to resolve.

Well, 888.geek is up and running using the "Blockchain DNS" extension on my Chrome browser. My site does not show up using the same extension for FireFox. By the way, it's a simple web page that says " 888.geek - coming soon..." To reach my website, you may have to type it in like this "http://888.geek/" You may have to include the forward slash at the end. However, now it seems like I don't have to include the foward slash at the end. I am still testing.

Overall, it works for me so far. However, getting maintream adoption and having these "ALT TLDs" work on the mainstream internet is another issue. This must be hassle-free and frictionless for the global public outside of the domain name community to accept. I am going to do my best to educate myself on what could be again, true internet land ownership.

Thank you for your time.

 

[DaveX]

Hello everyone. How are you? I think these "Alt TLDs" may present true internet land ownership. The idea that you or I can possibly own a TLD is something that eveyone needs to really take a hard look at.

So, I did my little test to see if these alternative TLDs can possibly work. First, I opened up my chrome browser and added the "Blockchain DNS" extension. Then I proceeded to https://members.opennicproject.org/ to sign up as a new user. I signed up and was sent a confirmation link in my email. Clicked on the link in my email and I was confirmed. Next, I went to http://be.libre/ and signed in with my OpenNic username and password to register a free .Geek domain name. I registered 888.geek (it was available), set the nameservers to my webhosting company of choice, and probably had to wait less than 24 hours for the nameservers to resolve.

Well, 888.geek is up and running using the "Blockchain DNS" extension on my Chrome browser. My site does not show up using the same extension for FireFox. By the way, it's a simple web page that says " 888.geek - coming soon..." To reach my website, you may have to type it in like this "http://888.geek/" You may have to include the forward slash at the end. However, now it seems like I don't have to include the foward slash at the end. I am still testing.

Overall, it works for me so far. However, getting maintream adoption and having these "ALT TLDs" work on the mainstream internet is another issue. This must be hassle-free and frictionless for the global public outside of the domain name community to accept. I am going to do my best to educate myself on what could be again, true internet land ownership.

Thank you for your time.

My thoughts exactly. So glad you were able to set that up with relative ease. It seems possible that the process could be developed for even more ease of use.