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

2021-05-12 Thread Stoffel, John (TAI)
: Service Now Self Service Portal -Original Message- From: Mark Andrews Sent: Wednesday, May 12, 2021 8:40 AM To: Stoffel, John (TAI) Cc: Tony Finch ; bind-users@lists.isc.org Subject: Re: ISC Bind as secondary to Windows Server: bad bitmap error on named xfer. There is enough information to

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

2021-05-12 Thread Mark Andrews
Now Self Service Portal > > > -Original Message- > From: Tony Finch On Behalf Of Tony Finch > Sent: Tuesday, May 11, 2021 7:13 PM > To: Stoffel, John (TAI) > Cc: bind-users@lists.isc.org > Subject: RE: ISC Bind as secondary to Windows Server: bad bitmap error on &g

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

2021-05-12 Thread Stoffel, John (TAI)
ubject: RE: ISC Bind as secondary to Windows Server: bad bitmap error on named xfer. 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 lik

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

2021-05-11 Thread Stoffel, John (TAI)
John (TAI) Cc: bind-users@lists.isc.org Subject: Re: ISC Bind as secondary to Windows Server: bad bitmap error on named xfer. 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

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. > www.cisco.toshiba.co

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

2021-05-11 Thread Stoffel, John (TAI)
..2..*T 65 16 1b 28 09 ac aa b3 41 f0 85 60 e6 e2 18 ae e..(A..` -Original Message- From: Tony Finch On Behalf Of Tony Finch Sent: Tuesday, May 11, 2021 5:24 PM To: Stoffel, John (TAI) Cc: bind-users@lists.isc.org Subject: Re: ISC Bind as secondary to Windows Server: bad

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, and

Re: named-xfer?

2009-04-02 Thread Michelle Konzack
G'evening, Am 2009-04-02 18:37:37, schrieb Matthew Pounsett: > dig IN AXFR zone @server > file > > that will do it. Thanks, it worked as expected. Uff! Thanks, Greetings and nice Day/Evening Michelle Konzack -- Linux-User #280138 with the Linux Counter, http://counter.li.org/

Re: named-xfer?

2009-04-02 Thread Matthew Pounsett
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02-Apr-2009, at 18:33, Michelle Konzack wrote: Hello, I have to fetch some zones from <http://www.zonedit.com/> but it seems, "named-xfer" does not more exist in bind9. How can I now manualy download a zone? dig IN A

named-xfer?

2009-04-02 Thread Michelle Konzack
Hello, I have to fetch some zones from <http://www.zonedit.com/> but it seems, "named-xfer" does not more exist in bind9. How can I now manualy download a zone? Thanks, Greetings and nice Day/Evening Michelle Konzack -- Linux-User #280138 with the Linux Counter, http: