Thursday August 07, 2008 Random ramblings
Thursday August 07, 2008 Weird BIND9 AXFR error? Remove stray A6 records..
Some release after BIND 9.2.1, its parser for A6 records appears to have broken. If you've ever experimented with A6, you might to go check you've expunged all occurrences from your zone files. Resultant symptoms include:
- Slave BIND servers fail to AXFR zone updates, reporting "transfer of ..... from .... : failed while receiving responses: unexpected end of input" in their log files.
- Manual AXFRs with dig gives the errors of ";; Warning: Message parser reports malformed message packet." and ";; communications error to ....: end of file".
Background: For many years, as I saw it only between a master behind a sub-1500 MTU (PPPoE, sigh) and certain servers, I assumed it was an MTU-blackhole problem with some upstream sneakily doing firewalling. However, recently the problem started to afflict another server, after an upgrade of their BIND software, and affected AXFRs even over paths that were perfectly fine. Some brute-force testing ruled out obvious problems like size issues (not like my zones are big) or relatively new records like SSHFP, leading to some head-scratching, but eventually pinned it down to a couple of stray A6 records.
( Aug 07 2008, 06:59:24 PM IST ) Permalink Comments [0]
Trackback URL: http://blogs.sun.com/paulj/entry/weird_bind9_axfr_error_remove
Comments:
Post a Comment:
