-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
My understanding is that you don't need this unless you're planning on
using hardware security modules. You can still generate and manage keys
without pkcs11.
See:
http://www.isc.org/software/bind/new-features/9.7
cv
Timothy Holtzen wrote:
> Has
Has anyone been able to get 9.7.1-P2 to build with pkcs11 and run on
RHEL/CentOS 5? I appear to be able to configure and make without any
problems but when I go to run it I get the following error in the log.
named[14899]: starting BIND 9.7.1-P2 -c /etc/named.conf -t /var/named/chroot
named[14899
My preference would be use a static NAT keep the RFC1918 address the same
and use static NAT to convert the global IP to RFC1918 IP address.
Gary
-Original Message-
From: bind-users-bounces+gladney=stsci@lists.isc.org
[mailto:bind-users-bounces+gladney=stsci@lists.isc.org] On Be
Overview
- internal DNS server with RFC1918 IP (old ip)
- wish to move to a global unique IP but still remain internal (new ip)
- keep the same name
Clients would still use the old IP until the migration had been completed.
What would be the preferred method to "forward" all requests from
the ol
I've also reported this as a bind bug, but I'm posting it here as I
think it answers the case for the BSD user in the thread entitled: Can't
get BIND to use GSSAPI from /usr/local on FreeBSD
(Patch attached which fixes it for me)
I've traced my problem to what looks like a mismatch of expect
5 matches
Mail list logo