From bert.hubert at powerdns.com Tue Feb 7 09:57:23 2017 From: bert.hubert at powerdns.com (bert hubert) Date: Tue, 7 Feb 2017 10:57:23 +0100 Subject: [Pdns-announce] PowerDNS Jobs, 4.1.x planning, research Message-ID: <20170207095723.GD6645@server.ds9a.nl> Hi everyone, In this post, we want to mention a few things: PowerDNS Jobs, 4.1 plans & some DNSSEC research. First, PowerDNS is growing rapidly as more and more large scale service providers displace closed DNS systems by PowerDNS, especially for security enhanced DNS and "parental control". More on this can be found here https://www.open-xchange.com/portfolio/ox-powerdns/ and here https://www.powerdns.com/platform.html We therefore have two job openings currently. Full details are on https://www.powerdns.com/careers.html , brief descriptions: * Solution Engineer Daily activities alternate between working on customer issues and actual Professional Services for customer implementations (both on-site and off-site). As Solution Engineer (with a focus on PowerDNS) you will work closely with the PowerDNS development team, as well as with other parts of Open-Xchange and Dovecot development, sales, and Product Management teams from within a European Services team. We think Support & Implementation is a great step into a promising career. We are specifically looking for employees willing to learn quickly while delivering great support and service, while keeping an eye towards growing within the Global Services department or into different roles in the larger Open-Xchange organisation. * Versatile frontend developer with moderate middleware skills We are looking for people with any or more of the following skills: - Modern web development (key words are AngularJS, JSON, RESTful, D3.js, Backbone and other frameworks that aren't TOO hip) - Django - Ability to enhance middleware in Python - Ability to propose changes to core C++ code and make small additions - Automated UI testing For more information, please head to https://www.powerdns.com/careers.html * 4.1 plans We have started the process of 4.1 release planning. We have identified a number of areas that need to be addressed, but your input is most welcome. The 4.0 roadmap process was rather successful, but only because users vocally reminded us of what was missing. So please let us know: what are we simply not talking about that you think is vital for PowerDNS. If we are not doing something, it is probably because we don't know that you need it! So please let us know whatever you are missing on powerdns-ideas at powerdns.com. * DNSSEC research We wrote some perhaps interesting stuff on DNSSEC here: https://ds9a.nl/hypernsec3/ With this technique, we've been able to measure the DNSSEC penetration on all top level domains (including co.uk and com.br). The list is here: https://powerdns.org/dnssec-stats/ All in all we have found there are around 7.4 million signed DNSSEC domains. Given what we know of the zones involved (.se, .nl, .de, .be), it looks like the majority of these are signed and mostly served by PowerDNS. From bert.hubert at powerdns.com Thu Feb 23 11:37:30 2017 From: bert.hubert at powerdns.com (bert hubert) Date: Thu, 23 Feb 2017 12:37:30 +0100 Subject: [Pdns-announce] PowerDNS Recursor 4.1 plans Message-ID: <20170223113730.GA30355@server.ds9a.nl> Hi everyone, In this message, we ask you to look at our intended PowerDNS Recursor 4.1 development plan. The 4.0 release train has been very successful and reliable for a major '.0' release and is seeing wide production use, including DNSSEC validation for millions of clients. However, we have found some things that need improving for the 4.1 release. This the focus for 4.1: general improvement of quality, rounding out of features, and adding a few specific new features. We ask you to take a REAL good look at what we intend to do. It is entirely possible that you are running into issues and challenges you are sure we know about already, when we in fact don't. So if the PowerDNS Recursor is somehow not making you happy, and what ails you is not in the list below, we would LOVE to hear from you! We are aiming for a June release of Recursor 4.1, but depending on developments this might be earlier or later, and possibly not with all features communicated below. This email is not a roadmap you can rely on. If you need to rely on certain features appearing by a certain time, please head to https://www.powerdns.com/contactform.html - for commercially supported customers we regularly commit to dates & features. Already addressed since last 4.0 release, so no need to ask for this: https://github.com/PowerDNS/pdns/issues/ #4988 - Add `use-incoming-edns-subnet` to process and pass along ECS #4990 - Native SNMP support for Recursor #5058 - Faster RPZ updates #4873 - Ed25519 algorithm support #4972 - 2017 root KSK added #4924 - EDNS Client Subnet tuning & length configuration All issues scheduled for 4.1 can be viewed on the rec-4.1.0 milestone on GitHub https://github.com/PowerDNS/pdns/milestone/7 Important highlights: Improvements: #5077 - DNSSEC validation is in need of a refactor (ongoing) #4000 - And other tickets: more love & performance for RPZ New features: #5079 - EDNS Client Subnet port number #5076 - RPZ persistency #440 - DNS prefetching #4662 - Continue serving expired cache data if all auths are down If you want to help, please check out the full milestone listing https://github.com/PowerDNS/pdns/milestone/7 and see if (your) older issues might have been addressed by now. Also, if you have an opinion on certain fixes, features or improvements, please add them to the GitHub issues so we learn about your concerns! Thanks!