Bug#918661: pdns-server: EDNS Compliance Steps
On Tue, 8 Jan 2019 22:24:21 +1100 Dean Hamstead wrote: The same results are given when tested against: pdns-server (3.4.1-4+deb8u8) pdns-server (4.0.3-1~bpo8+1) pdns-server (4.0.3-1+deb9u2) To get a clean slate on 4.0, you need to disable the packet cache. However, as Christian noted, the errors reported otherwise do not actually hurt production usage. Kind regards, -- Peter van Dijk PowerDNS.COM BV - https://www.powerdns.com/
Bug#918661: pdns-server: EDNS Compliance Steps
* Dean Hamstead [190108 13:02]: > The same results are given when tested against: > > pdns-server (3.4.1-4+deb8u8) > pdns-server (4.0.3-1~bpo8+1) > pdns-server (4.0.3-1+deb9u2) Just for the record, your ednscomp links do not work - I think they expire after a short time. I'll have to see for myself somewhere. 3.4.1 should be a lot worse EDNS wise, and 4.0.x should have no production EDNS0 issues. Chris
Bug#918661: pdns-server: EDNS Compliance Steps
The same results are given when tested against: pdns-server (3.4.1-4+deb8u8) pdns-server (4.0.3-1~bpo8+1) pdns-server (4.0.3-1+deb9u2) On 8/1/19 8:52 pm, Chris Hofstaedtler wrote: * Dean Hamstead [190108 05:03]: Version: 3.4.1-4+deb8u8 It seems that 'certain work arounds' are being removed on the 1st of Feb 2019 according to https://dnsflagday.net/ I have generated this report https://ednscomp.isc.org/ednscomp/154f9de8ce (nothing secret about it), but am not clear what step I should/can/need to take with powerdns. Google hasnt yielded results - please prove me wrong. Upgrading to Debian 9 would be the recommended solution. Chris
Bug#918661: pdns-server: EDNS Compliance Steps
* Dean Hamstead [190108 05:03]: > Version: 3.4.1-4+deb8u8 > > It seems that 'certain work arounds' are being removed on the 1st of Feb 2019 > according to https://dnsflagday.net/ > > I have generated this report https://ednscomp.isc.org/ednscomp/154f9de8ce > (nothing secret about it), but am not clear what step I should/can/need to > take with powerdns. Google hasnt yielded results - please prove me wrong. Upgrading to Debian 9 would be the recommended solution. Chris
Bug#918661: pdns-server: EDNS Compliance Steps
Package: pdns-server Version: 3.4.1-4+deb8u8 Severity: normal Dear Maintainer, It seems that 'certain work arounds' are being removed on the 1st of Feb 2019 according to https://dnsflagday.net/ I have generated this report https://ednscomp.isc.org/ednscomp/154f9de8ce (nothing secret about it), but am not clear what step I should/can/need to take with powerdns. Google hasnt yielded results - please prove me wrong. Your guidance is much appreciated Dean -- System Information: Debian Release: 8.11 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-042stab127.2 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages pdns-server depends on: ii adduser 3.113+nmu3 ii debconf [debconf-2.0] 1.5.56+deb8u1 ii init-system-helpers 1.22 ii libboost-program-options1.55.0 1.55.0+dfsg-3 ii libboost-serialization1.55.01.55.0+dfsg-3 ii libbotan-1.10-0 1.10.8-2+deb8u2 ii libc6 2.19-18+deb8u10 ii libcrypto++95.6.1-6+deb8u3 ii libgcc1 1:4.9.2-10+deb8u2 ii libgmp102:6.0.0+dfsg-6 ii liblua5.1-0 5.1.5-7.1 ii libpolarssl71.3.9-2.1+deb8u4 ii libsqlite3-03.8.7.1-1+deb8u3 ii libstdc++6 4.9.2-10+deb8u2 ii lsb-base4.1+Debian13+nmu1 ii ucf 3.0030 pdns-server recommends no packages. Versions of packages pdns-server suggests: ii pdns-backend-pgsql [pdns-backend] 3.4.1-4+deb8u8 pn pdns-recursor -- debconf information: * pdns-server/localaddress: 0.0.0.0 * pdns-server/allowrecursion: 127.0.0.1
