Codeberg seems to have vanished from DNS

51 points | by samip537 7 hours ago ago

14 comments

  • purpleidea 6 hours ago ago

    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.

    • JuniperMesos 4 hours ago ago

      It's bad that the DNS system is centralized; I wish that one of the blockchain-based decentralizing naming systems had caught on.

  • robin_reala 4 hours ago ago

    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.

  • stop50 6 hours ago ago

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

  • ErenayDev 5 hours ago ago
    • stop50 5 hours ago ago

      Codeberg uses secdns as dns server so i rewired my resolver to use them directly for the codeberg.org domain:

        2607:f740:e633:deec::2
        45.54.76.1
        157.53.224.1
      
      The ipv6 address is reused on both ns entries.
  • redstone_farm 6 hours ago ago

    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

  • derkades 3 hours ago ago

    It's back since 11:15 UTC!

  • __m 6 hours ago ago

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

    • stop50 6 hours ago ago

      Namesilo is the registrar

  • matt4401 6 hours ago ago

    same

  • Imustaskforhelp 6 hours ago ago

    Yup I am seeing the same issue too.

  • dennismenken 6 hours ago ago

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

  • joennlae 6 hours ago ago

    See the same on my side