Codeberg seems to have vanished from DNS

samip537 58 points 21 comments November 18, 2026
View on Hacker News

It seems that at 06:30 UTC today, Codeberg's registrar has placed them on clientHold, which has removed them from the .org zone entirely.

Discussion Highlights (11 comments)

joennlae

See the same on my side

Imustaskforhelp

Yup I am seeing the same issue too.

dennismenken

Same here. I don't think there will be any node issues.

__m

I guess we can rule out that ai caused it, unless namesilo is behind it.

redstone_farm

Stressful day for the Codeberg & Forgejo crew. > #codeberg's .org domain status is on "clientHold", I tried calling everyone that I could over there but no response from someone that can do something yet. ¯\_(ツ)_/¯ > > The domain didn't expire, so I'd expect the cause is different. I'd be curious to read the writeup afterwards. > > https://chaos.social/@n0toose/117636269217275094 > Attention: A #Forgejo security release is scheduled for today. The patches were temporarily publicly accessible as part of the release process. Due to urgent issues with #Codeberg, we are unable to proceed with the release. We are in contact with Codeberg and are working to find a solution. > > We therefore currently recommend that, if you are using the internal SSH server (Docker with `ssh.START_SSH_SERVER = true`), you disable it for the time being or prevent access to it. > > https://floss.social/@forgejo/117636334439245475

purpleidea

Apparently more and more registrars are "randomly" requiring clients to send copies of their passports and face selfies and other nonsense. I've heard namecheap is doing this and I emailed them and their answer was: > [snip] "It is correct that we do not require every customer to proceed with identity and payment verification. Unfortunately, we cannot specify the criteria; this information is internal." So randomly when they feel like it. Me and a number of customers are moving away from them immediately. Centralization of DNS is becoming a problem. Privacy rights are being trampled. Nobody should be collecting such images unless in emergencies, and they need to be liable when they misuse it.

stop50

Its apparently namesilo who did it: https://status.codeberg.eu/status/codeberg

ErenayDev

https://social.anoxinon.de/@codebergstatus/11763643784068884... IPv4 URL: http://217.197.84.140:443 IPv6: 2a0a:4580:103f:c0de::1 Also worth try the /etc/hosts hotfix: https://sauna.social/@sm/117636439190990385

robin_reala

https://social.wildeboer.net/@jwildeboer/117636595702972996 It seems that someone convinced the .org registrar that #codeberg is bad and so the domain name codeberg.org is currently on clientHold and thus removed from DNS.

derkades

It's back since 11:15 UTC!

ChrisArchitect

Some later discussion: https://news.ycombinator.com/item?id=50544261

Semantic search powered by Rivestack pgvector
13,334 stories · 126,150 chunks indexed