zackify
cli.rs domain has expired!
@zackify important this is renewed before some malicious entity purchases the domain and impersonates the various subdomains.
Nominus shows the domain as unavailable for purchase right now thankfully.
I am willing to pay the renewal fee if needed.
Nominus shows the domain as unavailable for purchase right now thankfully.
rnids.rs has a 30 day buffer after expiration before a domain is free for registration again
Judging by the number of issues linking here..
(sorry, couldn't resist!)
On a more serious note, once this current issue is resolved we should discuss the longer term governance of this service. Mainly about access to control the domain name as the usual OSS "just fork it" approach won't work here. It would seem sensible to have a few additional people have access.
hi i own this now. happy to point it at the right place and donate it to a proper organization.
@toddself Could you create a GitHub org as well as a new team on DigitalOcean (where the DNS is hosted right now)? I think it's the fastest way to get everything back up as-is.
The things we should do are
- get it running again
- create an "organization" so this doesn't happen again
- fix the open issues (e.g. a redirection service in addition to just CNAMEs)
I am willing to help with the DNS automation (if we need something more complex this is doable too) and fixing the other issues.
hi i own this now.
Would you be (financially) able to renew the domain right now? That will allow the (sub)domains to function again while the organizational issues are addressed.
I am waiting for my registrar (that would allow .rs domains -- my main one doesn't) to finalize the order.
If someone can give me the DNS details I'll update it as soon as I am able.
I created a new org in github (cli-rs) and invited everyone who has commented on this thread and forked the code into that org. I'll add a new org to my digital ocean account shortly
The DNS servers originally used for cli.rs, DigitalOcean, is still responding with the correct DNS records for cli.rs:
$ whois cli.rs
...
DNS: ns1.digitalocean.com -
DNS: ns2.digitalocean.com -
DNS: ns3.digitalocean.com -
$ dig cli.rs @ns1.digitalocean.com
...
;; ANSWER SECTION:
cli.rs. 3600 IN A 185.199.109.153
cli.rs. 3600 IN A 185.199.111.153
cli.rs. 3600 IN A 185.199.108.153
cli.rs. 3600 IN A 185.199.110.153
$ dig colmena.cli.rs @ns1.digitalocean.com
...
;; ANSWER SECTION:
colmena.cli.rs. 1800 IN CNAME zhaofengli.github.io.
This means that, for now, you can use the DigitalOcean nameservers to make all the cli.rs subdomains work again. Down the line, once all the organizational stuff has been figured out, someone can recreate all the appropriate DNS records from the domains directory of this repo.
It would probably be a good idea to automate this. DigitalOcean has an API to configure DNS records, probably other DNS providers have as well.
I am waiting for my registrar (that would allow .rs domains -- my main one doesn't) to finalize the order.
@toddself I was under the impression that @zackify gave you their registrar account. If you just attempted to register, I don't think the order would go through since the domain is still under the 30-day grace period and clientUpdateProhibited.
Well, we'll see what happens here! But there's an org now and when the clientUpdateProhibited has been removed, we can handle it from there.
As of 2h ago cli.rs is back:
Domain name: cli.rs
Domain status: Active https://www.rnids.rs/en/domain-name-status-codes#Active
Domain status: clientUpdateProhibited
https://www.rnids.rs/en/domain-name-status-codes#ClientUpdateProhibited
Registration date: 27.07.2020 22:50:01
Modification date: 04.08.2025 12:22:30
Expiration date: 27.07.2026 22:50:01
Confirmed: 27.07.2020 22:56:20
Registrar: Stanco d.o.o.
Registrant: Individual
Administrative contact: Individual
Technical contact: Individual
DNS: ns1.digitalocean.com -
DNS: ns2.digitalocean.com -
DNS: ns3.digitalocean.com -
DNSSEC signed: no
Whois Timestamp: 04.08.2025 14:25:31
I think Zack still owns the domain because the registrar is still StanCo and the DNS is still the same. what probably happened was that Gandi said that you could "buy" the domain (maybe they didn't read the Expiration date value properly, idk) when it had never dropped. I've had them do that to me in the past
Glad to see people jumping in to help on this :)
I emailed Zach yesterday. He replied quickly at 8:14 pm saying "I just renewed it now it should come back." Then at 8:21 pm he said "Keeps showing as unpaid on the ... domain provider even after I paid, will have to open a support ticket with them. Hopefully it just starts working soon." Thanks @zackify !
Sorry I missed these. They emailed me this morning they got my payment and it's back.
Maybe worth adding a small sponsor badge to the repo I didn't realize just how much interest there was in this little domain project!
Sorry it lapsed, if I do sponsor it and get some money I can prepay more years of it.
@zackify Thanks for renewing the domain! Going forward, would you consider bringing more people on-board so this is more resilient? Other people have provided similar suggestions above.
Note that I'm not advocating giving registrar access to many people - There is a level of trust involved since many project rely on this domain for identity.
yea, I think it's worth looking into maybe transferring the domain to the Rust Foundation or having them handle paying for the domain
Yeah I would be down to transfer to the rust foundation. Do you have any info on who I should reach out to?