home.social

#ripe_ncc — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #ripe_ncc, aggregated by home.social.

fetched live
  1. Главная уязвимость российских хостингов: как оплачивать членство RIPE NCC в 2026 году

    Хостинговые компании России устранили старые проблемы. Большинство хостингов стабильно держат соединения с крупными интернет-провайдерами (BGP-сессии с аплинками) и правильно объявляют свои IP-адреса в глобальной сети (route-объекты). Клиенты получают сервис высокого уровня без лагов. Однако все эти достижения могут в один момент разлететься на кусочки. Как защитить Ахиллесову пяту

    habr.com/ru/articles/1005092/

    #хостинг #хостингпровайдер #доменные_имена #доменная_зона #ripe_ncc #ripe #ripe_atlas

  2. Главная уязвимость российских хостингов: как оплачивать членство RIPE NCC в 2026 году

    Хостинговые компании России устранили старые проблемы. Большинство хостингов стабильно держат соединения с крупными интернет-провайдерами (BGP-сессии с аплинками) и правильно объявляют свои IP-адреса в глобальной сети (route-объекты). Клиенты получают сервис высокого уровня без лагов. Однако все эти достижения могут в один момент разлететься на кусочки. Как защитить Ахиллесову пяту

    habr.com/ru/articles/1005092/

    #хостинг #хостингпровайдер #доменные_имена #доменная_зона #ripe_ncc #ripe #ripe_atlas

  3. In 2018, a record with the wrong signature was resolved correctly on more than 50% of the probes.

    In the meantime, the number of Atlas probes active in .pl has probably decreased, and only well-maintained probes remain active, so the test is likely a bit skewed toward apparent spreading of DNSSEC deployment since neglected networks are less represented now. This means that networks that might still have poor validation could now be underrepresented.

    2/2

  4. In 2018, a record with the wrong signature was resolved correctly on more than 50% of the probes.

    In the meantime, the number of #RIPE Atlas probes active in .pl has probably decreased, and only well-maintained probes remain active, so the test is likely a bit skewed toward apparent spreading of DNSSEC deployment since neglected networks are less represented now. This means that networks that might still have poor #DNSSEC validation could now be underrepresented. #RIPE_NCC

    2/2

  5. In 2018, a record with the wrong signature was resolved correctly on more than 50% of the probes.

    In the meantime, the number of #RIPE Atlas probes active in .pl has probably decreased, and only well-maintained probes remain active, so the test is likely a bit skewed toward apparent spreading of DNSSEC deployment since neglected networks are less represented now. This means that networks that might still have poor #DNSSEC validation could now be underrepresented. #RIPE_NCC

    2/2

  6. Did you know ISC had a Hackathon recently? It was hosted by , , and in Stockholm on March 14-15. We proposed a project, the DNS Zone Viewer, to integrate another DNS implementation (besides 9) with Stork, our graphical management interface.

    Read more about it at isc.org/blogs/2025-dns-hackath !

  7. Did you know ISC had a #DNS Hackathon recently? It was hosted by #RIPE_NCC , #dnsoarc , and #Netnod in Stockholm on March 14-15. We proposed a project, the DNS Zone Viewer, to integrate another DNS implementation (besides #BIND 9) with Stork, our graphical management interface.

    Read more about it at isc.org/blogs/2025-dns-hackath !

  8. Did you know ISC had a #DNS Hackathon recently? It was hosted by #RIPE_NCC , #dnsoarc , and #Netnod in Stockholm on March 14-15. We proposed a project, the DNS Zone Viewer, to integrate another DNS implementation (besides #BIND 9) with Stork, our graphical management interface.

    Read more about it at isc.org/blogs/2025-dns-hackath !

  9. Did you know ISC had a #DNS Hackathon recently? It was hosted by #RIPE_NCC , #dnsoarc , and #Netnod in Stockholm on March 14-15. We proposed a project, the DNS Zone Viewer, to integrate another DNS implementation (besides #BIND 9) with Stork, our graphical management interface.

    Read more about it at isc.org/blogs/2025-dns-hackath !

  10. Ich habe endlich gelernt wann man #RIPE und wann man #RIPE_NCC sagt. Was about time.

    Hoffentlich ist es in Zukunft immer richtig.

  11. Ich habe endlich gelernt wann man #RIPE und wann man #RIPE_NCC sagt. Was about time.

    Hoffentlich ist es in Zukunft immer richtig.

  12. Ich habe endlich gelernt wann man #RIPE und wann man #RIPE_NCC sagt. Was about time.

    Hoffentlich ist es in Zukunft immer richtig.

  13. Ich habe endlich gelernt wann man #RIPE und wann man #RIPE_NCC sagt. Was about time.

    Hoffentlich ist es in Zukunft immer richtig.

  14. Do you want to be a (bigger) part of the open source DNS community?

    Come join ISC's Marcin Siodelski at the DNS Hackathon in Stockholm, sponsored by , , and ! We'd really appreciate your help, especially if you're a user.

    Get more details and sign up at isc.org/blogs/2025-dns-hackath , and thank you!

  15. Do you want to be a (bigger) part of the open source DNS community?

    Come join ISC's Marcin Siodelski at the DNS Hackathon in Stockholm, sponsored by #Netnod , #dnsoarc , and #RIPE_NCC ! We'd really appreciate your help, especially if you're a #Powerdns user.

    Get more details and sign up at isc.org/blogs/2025-dns-hackath , and thank you!

  16. Do you want to be a (bigger) part of the open source DNS community?

    Come join ISC's Marcin Siodelski at the DNS Hackathon in Stockholm, sponsored by #Netnod , #dnsoarc , and #RIPE_NCC ! We'd really appreciate your help, especially if you're a #Powerdns user.

    Get more details and sign up at isc.org/blogs/2025-dns-hackath , and thank you!

  17. Do you want to be a (bigger) part of the open source DNS community?

    Come join ISC's Marcin Siodelski at the DNS Hackathon in Stockholm, sponsored by #Netnod , #dnsoarc , and #RIPE_NCC ! We'd really appreciate your help, especially if you're a #Powerdns user.

    Get more details and sign up at isc.org/blogs/2025-dns-hackath , and thank you!

  18. @kkarhan @disarray @alyx @ripencc “AFAIK #RIPE_NCC only offers /24 to existing ASes with #IPv6 connectivity” it’s a bit different: as a member without any IPv4 allocation you can request a one-time /24 IPv4 allocation and your request is going to be put on the waiting list. The list is growing though: ripe.net/manage-ips-and-asns/i

  19. @kkarhan @disarray @alyx @ripencc “AFAIK #RIPE_NCC only offers /24 to existing ASes with #IPv6 connectivity” it’s a bit different: as a member without any IPv4 allocation you can request a one-time /24 IPv4 allocation and your request is going to be put on the waiting list. The list is growing though: ripe.net/manage-ips-and-asns/i

  20. @kkarhan @disarray @alyx @ripencc “AFAIK #RIPE_NCC only offers /24 to existing ASes with #IPv6 connectivity” it’s a bit different: as a member without any IPv4 allocation you can request a one-time /24 IPv4 allocation and your request is going to be put on the waiting list. The list is growing though: ripe.net/manage-ips-and-asns/i

  21. @kkarhan @disarray @alyx @ripencc “AFAIK #RIPE_NCC only offers /24 to existing ASes with #IPv6 connectivity” it’s a bit different: as a member without any IPv4 allocation you can request a one-time /24 IPv4 allocation and your request is going to be put on the waiting list. The list is growing though: ripe.net/manage-ips-and-asns/i

  22. « On m'a très souvent posé la question de comment j'ai pu avoir un AS(208069) et des #IPv6 pour ma Server Room. Aujourd'hui on va donc parler de #routage (#BGP), d'AS et d'IP. C'est parti ! » blog.ataxya.net/un-as-chez-soi

    Et en prime, n'oubliez pas le démon BGP du fédivers : botsin.space/@bgp/104427882726

    #LIR #RIR #RIPE_NCC

  23. « On m'a très souvent posé la question de comment j'ai pu avoir un AS(208069) et des #IPv6 pour ma Server Room. Aujourd'hui on va donc parler de #routage (#BGP), d'AS et d'IP. C'est parti ! » blog.ataxya.net/un-as-chez-soi

    Et en prime, n'oubliez pas le démon BGP du fédivers : botsin.space/@bgp/104427882726

    #LIR #RIR #RIPE_NCC