Codeberg.org Not Reachable
Codeberg.org, a nonprofit Git hosting platform, briefly vanished from the internet after its registrar NameSilo placed the domain in a “clientHold” status, apparently via the registrar’s abuse process and without prior notice to Codeberg. Commenters dissect how fragile DNS and registrar dependencies make even well-run services vulnerable to abrupt shutdowns, debate whether using cheap U.S.-based registrars and .org was a strategic mistake for a German organization, and propose mitigations such as multiple domains, local/EU registrars, self-hosting, or decentralized naming systems. Many see the incident as a warning about centralized control over domains and the growing tendency of registrars and registries to act as de facto censors or enforcement points.
Incident & Immediate Impact
- Codeberg’s primary domain,
codeberg.org, became unreachable when the registrar (NameSilo) placed it inclientHold, removing it from DNS. - Codeberg reported the domain had “disappeared” from their account, later learning it was suspended and sent to the registrar’s abuse team.
- Outage lasted a few hours; domain then began working again as caches expired. Codeberg stated they still had no official explanation from the abuse department at that time.
Workarounds During Outage
- Multiple users suggested adding Codeberg’s IPv4/IPv6 addresses to
/etc/hostsas a temporary fix, with reminders to verify TLS certificates for security. - Some proposed switching temporarily to another domain (e.g.,
codeberg.eu), but Codeberg said multi-domain support, SEO, and 2FA complexities made that low-value for a short outage.
Registrar Suspension, Policy & Process
- Whois showed
clientHoldandclientTransferProhibited, consistent with legal/abuse disputes or policy issues. - Posters debated possible causes: DNS abuse (malware, phishing, spam), invalid contact data, or mistaken/bogus reports. No consensus; ultimate reason remains unclear.
- Several described generally poor abuse-handling across registrars: sudden suspensions, weak communication, and even pay-to-unlock practices.
Registrar Choice, Jurisdiction & Cost
- Many criticized using a “cheap” US registrar for a critical EU-based FOSS service, arguing low-margin registrars underinvest in careful abuse review.
- Others countered that EU registrars and German courts can also mandate suspensions, especially for copyright, so this isn’t uniquely a US problem.
- Some recommended expensive enterprise registrars (e.g., those used by large tech firms) that reportedly resist takedowns without strong legal basis, noting cost may be prohibitive for a small non-profit.
Reliability, Redundancy & Alternatives
- Suggestions included:
- Multiple domains across different TLDs/registrars, though this risks confusing users and phishing lookalikes.
- Using national or EU TLDs (
.de,.eu) and local registrars to keep disputes within local courts. - Onion services, alternative DNS systems (Namecoin, ENS, GNS, Handshake), overlay networks (Tor, I2P, Yggdrasil), or pure IP access.
- Some argued full robustness requires “being your own registrar,” which is effectively unrealistic for most.
Broader Concerns About DNS Centralization
- Many saw this as evidence that DNS/registrars are a single point of failure increasingly used for deplatforming.
- Discussion touched on ICANN contracts, root zone control, and the tension between abuse mitigation and overzealous or mistaken takedowns.