8.2.2 -> 9.1.0 upgrade problems...

[Brad Knowles]

At 4:05 PM -0500 4/2/01, Christopher L. Barnard wrote:

>  I am currently upgrading from bind 8.2.2patch7 to 9.1.0 on Sun Solaris 7
>  servers.  I have done all of the nameservers in all of my subdomains, and
>  one of the two slave nameservers for my root domain.  However, if I try to
>  do the other slave and the master, they fail.

	If you're upgrading to BINDv9, make sure you upgrade to 
9.1.1-REL, not 9.1.0.

>  The problem is that with the primary and one of the slaves running
>  version 8.2.2patch7, all of the other servers are fine.  If I upgrade these
>  two to 9.1.0, they fail.  This makes it very hard to debug, because I cannot
>  leave the production nameserver busted, but it works fine on the remaining
>  root level slave and all six of the subzones.

	How about giving us some specific examples of how they fail?  Log 
entries showing the failure?  Without that kind of detail, it's going 
to be virtually impossible for anyone to help you debug this problem.

-- 
Brad Knowles, <brad.knowles at skynet.be>

/*        efdtt.c  Author:  Charles M. Hannum <root at ihack.net>          */
/*       Represented as 1045 digit prime number by Phil Carmody         */
/*     Prime as DNS cname chain by Roy Arends and Walter Belgers        */
/*                                                                      */
/*     Usage is:  cat title-key scrambled.vob | efdtt >clear.vob        */
/*   where title-key = "153 2 8 105 225" or other similar 5-byte key    */

dig decss.friet.org|perl -ne'if(/^x/){s/[x.]//g;print pack(H124,$_)}'