If dig (and named) would just print the record that broke things, it would help
a lot more. Or print more debug info on the parsing to show where it went off
the rails... I found it interesting that perl Net::DNS would pull down the
records, and kept going even though there was a problem.
In
There is enough information to reproduce. Dig does have +besteffort but it
doesn’t recover from this.
You don’t want default handling to accept broken records so just skipping isn’t
good behavior. It should be possible to extend +besteffort to print bad
records in unknown format.
--
Mark A
Tony,
A big thanks to you for your suggestion on using the Perl Net::DNS module,
using that, I was then able to run named-checkzone on the dumped file (35,000+
lines!) to find the one bad record which was making things crap out. I'm back
a bit on bind versions, but not that far back, so I would
3 matches
Mail list logo
