Skip Navigation
50 comments

  • Trolling aside, if the winner sets up SSL certs they could probably phish some reused passwords from HexBear users trying to login.

  • I must not understand it properly, how was the instance functioning during the grace period for the domain? I was under the understanding that the grace period still had the domain name disabled it's just the owner had the ability to renew it still

    then once the grace period ended then it hit redemption period where it's auctioned.

    If the domain expired 1/12, how was hexbear functioning for the last month(or was it not and I just didn't notice cause I don't interact with it)

    • still had the domain name disabled it's just the owner had the ability to renew it still

      There's no set rule, every registrar can handle it differently, some don't even bother to change the configuration at all until it's actually been resold

      There's also caching, the underlying servers are still responding to their raw IP addresses, DNS and registrars just tie the name to the IP address and then your device uses that IP address. Once you've been to a site your device (or firewall/router) will have that IP address/name cached and won't look it up again for awhile until the cache entry expires

      Lemmy federation can also be weird, it's not unheard of for some instances to take days to catch-up on federated posts from certain other instances.

      Startrek.website for example was just having a week long federation problem where they weren't getting external posts, even when an external user made a post directly to a comm on their instance

      • So I went to a little bit of a deep dive regarding this, they do require interrupting DNS as part of their Redemption grace period. Furthermore I went into the hexbear website and their current header indicates that despite the fact that it's in current auction the current owner can still sign in and redeem the domain. Which makes me think that they're running a more gracious rgp then what is to be expected. So that being said they could just be placing bids on a domain that won't actually sell.

        Being said though apparently according to other comments the infrastructure maintainer of hexbear has been AWOL for a while so it's entirely possible that they just won't notice it that it will transfer

        The way I see it, there's a few things that may have happened here.

        1. Either the domain registrar incorrectly processed their expired domain system and sold the domain without interrupting DNS in which case a third party bought it and then immediately put it to auction (unlikely cause the status / NS is the expired servers), this route would open up the domain registrar to a complaint being filed against them via ICANN
        2. Or their domain registrar had a 30-day preemptive period where they were messaging the person, and then an additional few days with auction rgp that's the actual official last call for it, if this is the case then hexbear's infrastructure admin should be able to just sign in and renew the domain, but they may be forced to pay a Redemption fee on top of it, if that's the case then when they renew the domain, the auction would continue running it's just when it ended no buyers would be selected because the original owner renewed
        3. Essentially the same thing as one, however they never disabled DNS, and instead of it being a third party, it's themselves putting it out to auction on the tail end of the 30-day rgp window. If that's the case then like number one they're in violation of ICANN as DNS wasn't disabled.

        Again though, this is off the consensus that they didn't disable DNS a month ago, which I'm leaning at because I haven't seen any comments regarding it nor have I found any ststus sites showing that the domain was offline

50 comments