XMPP Service Operators - 2024-01-22

  1. fjklp

    jabber.network is not able to resolve, which means that search.jabber.network is unavailable. The domain is still valid. Does anyone know anything about this?

  2. MattJ

    fjklp: search.jabber.network is back. jabber.network has never resolved.

  3. jonas’


  4. jonas’

    sorry for the outage (of sjn for instance) last night

  5. fjklp

    thanks for the notice MattJ

  6. jonas’

    there was a power outage caused by faulty equipment in the same rack my own server is located and it took the datacenter a while to get that sorted, and then it took me a while to get the services back up.

  7. jonas’

    but I used the chance to upgrade to bookworm, so there's that at least :)

  8. jonas’

    but I used the chance when everything was down anyway to upgrade the hypervisor to bookworm, so there's that at least :)

  9. Stefan

    Hello, It came out that I missed the "." in the dns entries. So they could not work! _service._proto.name TTL class SRV priority weight port target one could expand the explanation at that point and directly add the line: _service._proto.name.domain.tld. ("." !!) class SRV ... I didn't get the existence of that point at all, simply over-read it.

  10. Licaon_Kter

    That's usually added by the DNS panel thing

  11. Stefan

    my provieders "thing" seems to be buggy.

  12. BTNC

    > Who is the operator or associated with the "b1t.rip" server. Rewtkid is who he usually goes by from jab.nullexistence.net he DDOSd digdeeper.club over removal of a spammer who even hit this muc and many more.

  13. latex

    What kind of DDoS attack was it?

  14. latex

    L3, L7?

  15. latex

    TCP SYN? Bandwidth attack? UDP amplification? DNS amplification? Botnet?

  16. agris

    1. Million N-words

  17. BTNC

    Logs would have to be looked at. Its not his first time. agris the million n words is a different person from the kni$$er spammer

  18. agris