ISC BIND 9 (@bind9) header
ISC BIND 9 (@bind9) profile picture

ISC BIND 9

@bind9

Classic, full-featured DNS software system from Internet Systems Consortium. Find us at https://teapawt.net/t.co/nXWGkH25FH

 www.isc.org
isc.org/downloads/bind
Joined July 2017
  • Tweets286
  • Following129
  • Followers911
12Media
Photo by ISC BIND 9 (@bind9)Photo by ISC BIND 9 (@bind9)Photo by ISC BIND 9 (@bind9)Photo by ISC BIND 9 (@bind9)Photo by ISC BIND 9 (@bind9)Photo by ISC BIND 9 (@bind9)Photo by ISC BIND 9 (@bind9)Photo by ISC BIND 9 (@bind9)Photo by ISC BIND 9 (@bind9)Photo by ISC BIND 9 (@bind9)
If the EU cyber resilience act (CRA) and product liability directive (PLD) are the answers to software cyber security, what were the questions? #FOSDEMpublic #cybersecurity #regulation #law
Image from Robert Carolina (@Rob2yall)
1
12
1
19
2,199
Looking to improve performance of your #UDP server? Read my article about #BPF based load balancing for UDP traffic: pavel.network/rocky-road-tow…

Rocky road towards ultimate UDP server with BPF based load balancing on Linux: part 2

In first part of this article we evaluated multiple possible options to load balance UDP traffic between multiple sockets using SO_REUSEPORT capability. Due to nature of traffic in my particular case...

pavel.network
3
11
26
2,513
ISC BIND 9 retweeted
VERISIGN (@VERISIGN) profile picture
VERISIGN
@VERISIGN10 Aug 2023
#DidYouKnow #DNSSEC adoption is on the rise? To help it continue to grow, Verisign’s TLDs will soon undergo an important security enhancement. Check out Fellow Duane Wessels’ blog to learn more: blog.verisign.com/security/d… @packetpusher #cryptography
Verisign Will Help Strengthen Security with DNSSEC Algorithm Update - Verisign Blog

Verisign Will Help Strengthen Security with DNSSEC Algorithm Update - Verisign Blog

An important security enhancement will change the algorithm Verisign uses to sign top-level domains (TLDs) with Domain Name System Security Extensions (DNSSEC).

blog.verisign.com
1
7
2
19
4,245
ISC BIND 9 retweeted
DNS-OARC (@dnsoarc) profile picture
DNS-OARC@dnsoarc25 May 2023
📢 OARC 41 Call for Presentations Reminder! 📢The submission deadline for presentations at the upcoming #OARC41 workshop is approaching! 🗓️ Deadline: 2 weeks from today! 10 Jun 2023⏰🔗 Submit Your Proposal: Visit the OARC 41 website at [buff.ly/3NmsFys] #LoveDNS ^RP
Image from DNS-OARC (@dnsoarc)
Image from DNS-OARC (@dnsoarc)
4
3
465
Tony Finch @fanf is digging up where all those respectable clock management institutions are getting their time from #RIPE86
Image from Dmitry Kohmanyuk (@dk379)
5
10
1,493
Replying to @marcodavids
Aahhh. First of all, I know that you know, and you know that I know you know….. there is no good reason. But also, we started trying to overhaul the ARM and got sidetracked before we got to that chapter.
1
6
195
ISC BIND 9 retweeted
powerdns (@powerdns) profile picture
powerdns@powerdns11 Nov 2022
FOSDEM 2023 DNS Developer Room Call for Participation blog.powerdns.com/2022/11/11…
4
7
Replying to @CCBalert @ISC
FYI the ISC Twitter account is @ISCdotORG, you have tagged someone else. Also, these memory leaks are mostly limited to specific configuration options, so this is not the one to be banging drums about. But you are right, users should stay on top of the updates!
1
I am extremely happy to see that @IVA1919 is awarding my friend Peter Löthberg the gold medal for his work with Internet in Sweden. iva.se/publicerat/ivas-guldm…
7
8
47
Replying to @BlazejKrajnak
Actually we have looked at it at the time when the issue was created, couldn't reproduce, and now there is a comment on the ticket with some good debug information.
Replying to @JPMENS
We have that on our radar (gitlab.isc.org/isc-projects/…) and the refactoring we are doing now of the 'stream' protocols will help implement it. Feel free to upvote that - we need to hear that ppl want it!
1
Going to Philly and going by train. It just made the most sense!
@IETF (@ietf) profile picture@IETF@ietf10 Jul 2022
REMINDER: #IETF114 meeting (23-29 July 2022) standard registration deadline is 23:59 UTC on 11 July. The final agenda has more than 100 working group and other sessions, with an #IETFHackathon on 23-24 July. More info and registration details at: ietf.org/how/meetings/114/
Image from @IETF (@ietf)
4
1
6
Load more