home.social

#dnsoarc — Public Fediverse posts

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

  1. With the help of Scotland 🏴󠁧󠁢󠁳󠁣󠁴󠁿's favorite Pleisiosaur, I will be presenting some #DNS pre-history at #OARC46 in Edinburgh this Sunday, and I will be at #RIPE92 all next week.

    indico.dns-oarc.net/event/56/c

    Excited that two of the international events that have been a huge part of my career are coming to the city I grew up in !
    #dnsoarc #ripe

  2. I'm looking forward to attending OARC 46 in Edinburgh this weekend - 16th & 17th May!

    Excited to be reconnecting with the DNS community and catching up with friends and peers across the industry. I particularly enjoy the discussions, insights, and hallway conversations that make DNS-OARC events so valuable.

    Let's connect and chat

    #DNSOARC #OARC46 #DNS #Edinburgh @dnsoarc

  3. I'm looking forward to attending OARC 46 in Edinburgh this weekend - 16th & 17th May!

    Excited to be reconnecting with the DNS community and catching up with friends and peers across the industry. I particularly enjoy the discussions, insights, and hallway conversations that make DNS-OARC events so valuable.

    Let's connect and chat

    #DNSOARC #OARC46 #DNS #Edinburgh @dnsoarc

  4. I'm looking forward to attending OARC 46 in Edinburgh this weekend - 16th & 17th May!

    Excited to be reconnecting with the DNS community and catching up with friends and peers across the industry. I particularly enjoy the discussions, insights, and hallway conversations that make DNS-OARC events so valuable.

    Let's connect and chat

    #DNSOARC #OARC46 #DNS #Edinburgh DNS-OARC

  5. I'm looking forward to attending OARC 46 in Edinburgh this weekend - 16th & 17th May!

    Excited to be reconnecting with the DNS community and catching up with friends and peers across the industry. I particularly enjoy the discussions, insights, and hallway conversations that make DNS-OARC events so valuable.

    Let's connect and chat

    #DNSOARC #OARC46 #DNS #Edinburgh DNS-OARC

  6. Anyone else noticed that #DNSOARC actually has their code repositories on #Codeberg? Interested folks can check their page here

    #DNS #FOSS #OpenSource

  7. Have airlines just given up on making their websites work ? Hard to say which of BA or UA was worst today. Sluggish, browser seize-ups, random fails, won't accept valid addresses or credit card number formats. And overpriced.

    Anyway, see folks in Stockholm for #DNSOARC 45 and AGM.

  8. 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 !

  9. @shaft During review I asked why burn a flag for this (and not use an extension like everything else) as flags are supposed to be for generic needs. The answer was basically "no one said anything before, so this should be fine". The NXDOMAIN suppression is the more worrisome part as it does have consequences downstream. It supposedly passed the working group without issues, so here we are. There is a nice presentation about the subject in latest #DNSOARC by Shumon: indico.dns-oarc.net/event/52/c

  10. I hope the next DNS-OARC meeting will take place in Europe.
    #dnsoarc #lovedns

  11. 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!

  12. Sadly missing another OARC #dnsoarc workshop this week, but at least for the first time in 2 years I get to do so by choice. Taking a chance to dodge the northern winter & explore Brazil 😎
    Wishing everyone a successful OARC44 and NANOG93 in Atlanta, look forward to seeing people at RIPE90 in Lisboa (even if I haven't learned much Portuguese..)

  13. ISC was at over the weekend, and is gearing up for this week, in Prague. Last night we got together with some friends from RIPE, nic .AT, NetDEF, IBM, and the Ehrlang Foundation for a vegetarian-DNS dinner.

  14. Apparently, there is a #DNSSEC related issue on the #Liberia #ccTLD lr.. To quote: "All of the systems [...] have been shut down". Quite a hefty statement on the #DNSOARC mailing list. Haven't digged into it, but couldn't operators temporarily disable the DNSSEC validation?

    Curious if there will be any updates or a post-mortem.

    #DNS #TLD #infosec

  15. Problems with the c root servers for a few days now.

    The root servers {a,b,d-m}.root-servers.net all have a serial number of 2024052200 in their SOA record. Just dig @c.root-servers.net . SOA shows that the SOA serial is outdated showing the serial 2024052101.

    gov. even stopped their key transitioning process to wait for the c server to resolve their issues. Topic is discussed on the mailing list of DNS-OARC - a list worth to subscribe to.

    #dns #dnsoarc

  16. During my lunch break, I watched the #DNS4EU update of DNS-OARC 41 earlier this year. Since the company responsible for operating the DNS4EU project is Czech, it comes at no surprise that they consider #KnotDNS as part of their infrastructure. Yet, in the talk it does not sound like they settle on software diversity, and predominantly consider the (pretty reliable) Czech resolver.

    From other folks, I heard that software diversity is just one of the resiliency features among ASN diversity, geographical diversity, etc. Why is this not highlighted in the "scope, timeline and challenges" talk on DNS4EU?

    Slides and talk.

    #DNS #europe #dnsoarc #resiliency #privacy

  17. These releases included two vulnerabilities that affected many DNS implementations. Disclosure of these vulnerabilities had to be coordinated across multiple parties. We thank for providing the collaboration infrastructure, and the researchers and other DNS development teams for their cooperation and support.

  18. Just read on the #dnsoarc list that this issue persists for around 1 hour. Does it usually take that long to fix some #DNSSEC related issue? Some reference cases that can be linked?