Re: Changes to named between 7.0 and 9.2?

This is getting ever more bizarre  - my 9.2 installations both failin xactly the same
way, but /etc/openssl in one case is empty, in the other has lots going on.

Do you - or does anyone else - know how to produce a TSIG that can be inspected,
base64-decoded, and compared?  The related manpages are so dense, I can't find a way to
get any purchase on the problem.

I'm very gratefulto you for sticking with this.   My wildcard certificate runs out
tomorrow :-(

--
Steve Blinkhorn <[email protected]>

You wrote:
> 
> [email protected] (Steve Blinkhorn) writes:
> 
> > I only have NetBSD and Windows 10 machines.  I have tried the nsupdate from all my NetBSD machiness, a mix of: i386-7.0 amd64-7.0 amd64-8.0_RC1
> > and amd64_9.2.  It only fails from the 9.2 machines, which suggests to
> > me that the server setup is fine, but something is wrong with openssl
> > on my 9.2 installations.  In my named.conf file I have:
> >         allow-update {key "update";};
> > to grant the update permission for testing purposes.
> >
> > I can well believe that something is wrong with the 9.2 installations
> > (therre have been other problems) and that maybe a configurtion file
> > needs attention.  But what and where?
> >
> > --
> > Steve Blinkhorn <[email protected]>
> 
> 
> I found some time while watching paint dry (pkgsrc builds running) to
> install a VirtualBox VM of the 9.2 build from ftp.netbsd.org.
> 
> I had no trouble using the 9.2 build against a NetBSD/amd64 8.0_STABLE
> with BIND 9.10.5 from an older pkgsrc.  I did have to make sure I used
> the IPv4 address of the DNS server on the VirtualBox VM, as the
> VirtualBox VM didn't have IPv6 configured, so the nsupdate "server
> <hostname>" thing pulled the wrong address and of course, this was all
> NAT'ed out my laptop.  But it all worked as expected with nsupdate.
> 
> 
> 
> 
> -- 
> Brad Spencer - [email protected] - KC8VKS - http://anduin.eldar.org
>