Hi folks...after a little experimentation today I've discovered
certain files are no longer used in a linux chroot.
Linux kernel versions 2.6.2x.
Bind versions tested were 9.6.1-P3 and 9.7.0, both compiled from src
(not distro pkgs), and started with:
/usr/sbin/named -t /var/named -u username
Use
Hello everyone,
I tried to install BIND 9.7.0 from www.sunfreeware.com on a Solaris 10, x86
machine that was running before BIND 9.6.1-P1 with no problems.
The new install goes to the same directories, but for some reasons when I
run named-checkconf for my default /etc/named.conf file I get:
In message , "ic.nssip"
writes:
> Hello everyone,
>
> I tried to install BIND 9.7.0 from www.sunfreeware.com on a Solaris 10, x86
> machine that was running before BIND 9.6.1-P1 with no problems.
>
> The new install goes to the same directories, but for some reasons when I
> run named-checkco
Hi Mark,
This is what I suspect too.
Syslog gives me this record when I start BIND:
named[14380]: [ID 873579 daemon.notice] built with '--with-openssl=yes'
'--enable-largefile' '--sysconfdir=/usr/local/etc'
'--localstatedir=/usr/local/var' 'CC=gcc'
'CFLAGS=-O2 -L/usr/local/lib -R/usr/local/l
On 02/18/10 16:20, ic.nssip wrote:
Hi Mark,
This is what I suspect too.
Syslog gives me this record when I start BIND:
named[14380]: [ID 873579 daemon.notice] built with '--with-openssl=yes'
'--enable-largefile' '--sysconfdir=/usr/local/etc'
'--localstatedir=/usr/local/var'
Since no PREFIX w
Please comment!
Eugene
===
HOW TO CONFIGURE AUTO-SIGNED DYNAMIC ZONES WITH BIND9
This document describes how to configure bind9 to
automatically sign zones as they are being modified
by dynamic update mechanism. It is assumed that
you already know how
6 matches
Mail list logo