RE: ISC Bind as secondary to Windows Server: bad bitmap error on named xfer.

2021-05-12 Thread Stoffel, John (TAI)
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.

Re: ISC Bind as secondary to Windows Server: bad bitmap error on named xfer.

2021-05-12 Thread Mark Andrews
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

RE: ISC Bind as secondary to Windows Server: bad bitmap error on named xfer.

2021-05-12 Thread Stoffel, John (TAI)
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

RE: ISC Bind as secondary to Windows Server: bad bitmap error on named xfer.

2021-05-11 Thread Stoffel, John (TAI)
Tony, Thank you so much for your help! Your suggestion to use Net::DNS really saved the day, because then I could do a brute force binary search to find the broken DNS record which was screwing me up. Once I deleted that record, all was well in the world, and my AXFR transfers happened just

RE: ISC Bind as secondary to Windows Server: bad bitmap error on named xfer.

2021-05-11 Thread Tony Finch
Stoffel, John (TAI) wrote: > > And it does dump some errors too, which hopefully will give me an idea > of where my crappy bad record is located, and no use hiding crap: yuck, this looks like no fun... > www.cisco.toshiba.com. 3600IN CNAME redirect.toshiba.com. >

RE: ISC Bind as secondary to Windows Server: bad bitmap error on named xfer.

2021-05-11 Thread Stoffel, John (TAI)
Tony, Thank you for your help. I was going *insane* trying to figure out where this was coming from, and I had literally just pulled down the source to look at the code. So now it looks like I need to find and kill any and all NXT records in my domain. Sigh... So it's part of the DNSSEC

Re: ISC Bind as secondary to Windows Server: bad bitmap error on named xfer.

2021-05-11 Thread Tony Finch
Stoffel, John (TAI) wrote: > failed while receiving responses: bad bitmap > > None of my googling has given me any hints on what this error could be. I had to look at the source, which told me it's to do with NXT records which are super obsolete, so I wonder what weird stuff is in the zone that

ISC Bind as secondary to Windows Server: bad bitmap error on named xfer.

2021-05-11 Thread Stoffel, John (TAI)
Hi, I'm setting up an ISC Bind 9.11.20-RedHat-9.11.20-5 on a CentOS 8.3.2011 server and I'm running into a problem transferring a domain from our primary to this new secondary. The primary is a Windows Server 2012R2 system. I have 300+ domains setup and most of them are working just fine,