[Pdns-users] New PowerDNS employee, the importance of testing RCs, skipping 3.7.0, World Hosting Days 2015
Hi everybody, Some assorted remarks PowerDNS news: 1) New employee 2) Please test our release candidates 3) 3.7.0 has been skipped, all hail 3.7.1 4) World Hosting days in Germany New employee To start with, the great news is that on March 2nd, Pieter Lexis will be joining PowerDNS as a fulltime employee! Pieter wrote a paper and software on DANE under our mentorship while at the OS3 program at the University of Amsterdam, and later did an amazing job converting our documentation to the splendor you can now find on http://doc.powerdns.com/ Based on this work, we offered Pieter a job and we're very happy he accepted! Pieter (not to be confused with existing employee Peter) will focus on helping customers, improving our code infrastructure, fixing bugs and working on internet standards relevant for DNS. Release candidates -- When we work on a PowerDNS release, once we feel that it is ready to be used, we issue a Release Candidate. This is something you can run in production, and we expect it to work fine. If you have issues with an RC, we'll jump on them and resolve them as quickly as is possible. In the 3.7.0 release process this worked well, and because RC1 and RC2 saw wide deployment, many small issues were found before the actual release. 3.7.0 was looking good, and we tagged it for release. And then PowerDNS user packager Ralf van der Enden reported that the 3.7.0 we uploaded did exactly nothing on his FreeBSD system. After intense debugging to see if we could save 3.7.0, we found that we indeed had a bug which meant 3.7.0 compiled on FreeBSD, but did nothing. This was fixed. Today, we are increasing our regression tests to run on FreeBSD as well to prevent a repeat of this. But we'd like to urge our users, especially the ones on less mainstream platforms than Debian, Ubuntu, Fedora and Red Hat, to test our release candidates. This is one of the best ways you, like Ralf did, can help us deliver quality products! 3.7.0 will be skipped - Because we had uploaded 3.7.0 and had it built for our various platforms, we are not going to slip the FreeBSD fix into 3.7.0 and end up with two different 3.7.0 releases. The next PowerDNS Recursor release will be 3.7.1. This release is imminent, after we complete our FreeBSD regression testing. World Hosting Days 2015 in Rust --- PowerDNS and several of our Certified Consultants will be at World Hosting Days 2015 in Rust, Germany (March 24-26). As always, we enjoy meeting with PowerDNS users. If you or your management will be there and want to talk, please let us know! Kind regards, Bert PowerDNS ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
[Pdns-users] Recursor 3.7.1 released
Hi everybody, We're pleased to announce the final release for 3.7.1. RC1 and RC2 have seen a lot of production use already, which uncovered a small number of issues which have been addressed in this release. We are very grateful for the people that test our RCs, it really helps us deliver very reliable and robust formal releases. Thanks! As noted in a separate announcement earlier today (http://blog.powerdns.com/2015/02/12/new-powerdns-employee-the-importance-of-testing-rcs-skipping-3-7-0-world-hosting-days-2015/), 3.7.0 has been skipped and we are now releasing 3.7.1 instead. More information about 3.7.1 can be found in our blogpost: http://blog.powerdns.com/2015/01/22/an-introduction-to-powerdns-recursor-3-7-0/ 3.7.1 offers significant performance improvements when using IPv6 for outgoing queries, which is only on if query-local-address6 is set to something. Secondly, we spent a lot of time with very large PowerDNS deployments to preemptively improve our resilience against difficult or malicious traffic. To further enhance our resilience, the Lua module has been enhanced with new (bulk automated) filtering abilities. This version of the Recursor can also publish live performance graphs and a realtime overview of (attack) traffic per domain name. A demo of this can be seen on https://xs.powerdns.com/tmp/powerdns-recursor-live.gif . This is an early development, but to try this out, consult https://github.com/ahupowerdns/recuweb Tar.gz and packages are available on: * https://downloads.powerdns.com/releases/ * Soon: https://www.monshouwer.eu/download/3rd_party/pdns-recursor/ (RHEL/CentOS, with the usual huge thanks to Kees Monshouwer). The changelog with clickable links can also be found on https://doc.powerdns.com/md/changelog/#powerdns-recursor-371 This version contains a mix of speedups and improvements, the combined effect of which is vastly improved resilience against traffic spikes and malicious query overloads. PowerDNS Recursor 3.7.1 Released February 12th, 2015. This version contains a mix of speedups and improvements, the combined effect of which is vastly improved resilience against traffic spikes and malicious query overloads. Of further note is the massive community contribution, mostly over Christmas. Especially Ruben Kerkhof, Pieter Lexis, Kees Monshouwer and Aki Tuomi delivered a lot of love. Thanks! Minor changes: * Removal of dead code here and there [399]04dc6d618 * Per-qtype response counters are now 64 bit [400]297bb6acf on 64 bit systems * Add IPv6 addresses for b and c.root-servers.net hints [401]efc259542 * Add IP address to logging about terminated queries [402]37aa9904d * Improve qtype name logging [403]fab3ed345 (Aki Tuomi) * Redefine 'BAD_NETS' for dont-query based on newer IANA guidance [404]12cd44ee0 (lochiiconnectivity) * Add documentation links to systemd unit [405]eb154adfd (Ruben Kerkhof) Improvements: * Upgrade embedded PolarSSL to 1.3.9: [406]d330a2ea1 * yahttp upgrade [407]c29097577 [408]c65a57e88 (Aki Tuomi) * Replace . in hostnames by - for Carbon so as not to confuse Metronome [409]46541751e * Manpages got a lot of love and are now built from Markdown (Pieter Lexis) * Move to PolarSSL base64 [410]488360551 (Kees Monshouwer) * The quiet=no query logging is now more informative [411]461df9d20 * We can finally bind to 0.0.0.0 and :: and guarantee answers from the correct source [412]b71b60ee7 * We use per-packet timestamps to drop ancient traffic in case of overload [413]b71b60ee7, non-Linux portability in [414]d63f0d836 * Builtin webserver can be queried with the API key in the URL again [415]c89f8cd02 * Ringbuffers are now available via API [416]c89f8cd02 * Lua 5.3 compatibility [417]59c6fc3e3 (Kees Monshouwer) * No longer leave a stale UNIX domain socket around from rec_control if the recursor was down [418]524e4f4d8, ticket #2061 * Running with 'quiet=no' would strangely actually prevent debug messages from being logged [419]f48d7b657 * Webserver now implements CORS for the API [420]ea89a97e8, fixing ticket #1984 * Houskeeping thread would sometimes run multiple times simultaneously, which worked, but was odd [421]cc59bce67 New features: * New root-nx-trust flag makes PowerDNS generalize NXDOMAIN responses from the root-servers [422]01402d568 * getregisteredname() for Lua, which turns 'www.bbc.co.uk' into 'bbc.co.uk' [423]8cd4851be * Lua preoutquery filter [424]3457a2a0e * Lua IP-based filter (ipfilter) before parsing packets [425]4ea949413 * iputils class for Lua, to quickly process IP addresses and netmasks in their native format * getregisteredname function for Lua, to find the registered domain for a given name * Various new ringbuffers:
Re: [Pdns-users] Modify Records Table-Time of Day records
Martin Chandler wrote: Is it possible to modify the structure of the records table, to add new fields? You can add as many columns as you need; that will not interfere with PowerDNS Auth operation. (You can also rename existing columns, but you'd need to redefine the queries PowerDNS uses, so I don't recommend you doing that.) Even if you rename columns, etc it is also possible to then create a view for PowerDNS that matches the recommended schema. That way you don't have to redefine the queries... Yes, and no. Don't be surprised if things don't work anymore, depending on your setup. PDNS needs to write into the database/records table for several applications, and a view is not neccesarily writeable, depending on how it is created. Notably here would be Superslave operation; or probably any slave operation mode where replication is done by AXFR and not database means, as the transferred RRs need to be inserted into the DB at the slave. So, despite having a view representing the original database layout, you still may have to redefine some queries. On a side note: Dear staff, I am lacking to find the empty-non-terminal-queries at https://doc.powerdns.com/md/authoritative/backend-generic-mypgsql/ - did they become obsolete in recent revisions? Sebastian ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
[Pdns-users] Currently using distro packages, want to update
I try to always use software packages from my distro package managers (OpenSUSE zypper and CentOS yum) when I can, because it's easier and it resolves all my dependencies for me. I pretty much never manually deal with RPMs (so please forgive some of my ignorance). But my distro is currently on PDNS Authoritative 3.1, and upgrading my OS isn't anywhere on my radar right now. I want to get to 3.4.2, so (I think) I'll need to forego the package manager and install the RPM packages manually (if there are alternatives, I'm all ears). Some questions: - Since I won't have auto dependency management, what dependencies do I need installed to install PDNS from RPM? - Does pdns-static-3.4.2-1.x86_64.rpm _just_ install the binaries, or does it install the service, too, so that I can call `service pdns start` and configure the service to start automatically on boot? If the RPM doesn't do that, is there documentation / what is the recommended way to install PDNS as a service when installed manually with an RPM? - Should I just be able to uninstall the package using my package manager and then install the RPM as a drop-in replacement? Thanks in advance for putting up with my lack of knowledge! Nick ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] Currently using distro packages, want to update
Nick Williams wrote: I try to always use software packages from my distro package managers (OpenSUSE zypper and CentOS yum) when I can, because it's easier and it resolves all my dependencies for me. But my distro Which is your distro? Vendor and exact version number? For openSUSE I'm trying to keep up with powerdns releases and my submissions most times end up here pretty soon: https://build.opensuse.org/package/show/server:dns/pdns (currently pdns-3.4.2) https://build.opensuse.org/package/show/server:dns/pdns-recursor (currently pdns-recursor-3.6.2, 3.7.1 is in my home project but not built yet) Sooner or later this will be passed downstream in openSUSE Factory for the next openSUSE release. You can see here which platforms are enabled for default builds: https://build.opensuse.org/project/repositories/server:dns There you will also find the direct download links to zypper repo for your openSUSE version. In my OBS home project I'm also building openSUSE Factory_ARM for running the packages on rasperry pi. Ciao, Michael. smime.p7s Description: S/MIME Cryptographic Signature ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
