Ticket #363 (closed defect: worksforme)

Opened 2 years ago

Last modified 8 months ago

Regression between 2.9.20 and 2.9.22 ;; Got bad packet: extra input data on AXFR

Reported by: anon Owned by: ahu
Priority: normal Milestone:
Component: auth Version: 3.0
Severity: normal Keywords:
Cc:

Description

somewhere between versions 2.9.20 and 2.9.22 AXFR realisation was broken.

I have a zone with about 20k records. master server powerdns, 2 slaves - bind9 after upgrading to version 2.9.20 slaves stop refreshing zones.

I've check zone transfer using dig it says -

;; Got bad packet: extra input data 2401 bytes 4e b7 84 00 00 01 00 64 00 00 00 00 02 61 7a 00 N......d.....az. 00 fc 00 01 03 7a 65 72 c0 0c 00 02 00 01 00 01 .....zer........

and so on.

downgrading powerdns to 2.9.20 solves the problem. So i think that between versions 2.9.20 and 2.9.22 something in AXFR processing was broken.

My servers works under FreeBSD, but checking with debian package shows same result.

Change History

follow-up: ↓ 2   Changed 2 years ago by ahu

  • owner changed from somebody to ahu
  • status changed from new to assigned

Please reproduce against the 3.0 prereleases available through www.powerdnssec.org ! We will probably not fix 2.9.22.

in reply to: ↑ 1   Changed 2 years ago by anon

Replying to ahu:

Please reproduce against the 3.0 prereleases available through www.powerdnssec.org ! We will probably not fix 2.9.22.

I've tried pdns-static_3.0-rc2-1_amd64.deb - same shit

  Changed 13 months ago by peter

  • version set to 3.0
  • component changed from component1 to auth

We need more information to reproduce. Please provide configurations, zone file contents, etc.

  Changed 8 months ago by ahu

  • status changed from assigned to closed
  • resolution set to worksforme

I suggest running 'pdnssec test-zone' on the zone in question, it will most likely find a malformed record.

Note: See TracTickets for help on using tickets.