+--On 30 mars 2015 17:13:15 -0700 Kevin Oberman rkober...@gmail.com wrote:
| Note that chroot has just been re-enabled in the FreeBSD BIND ports. It's
| not default, so you must select the CHROOT option. This was just
| announced last week, and I am not sure the change has actually been
|
+--On 30 mars 2015 19:32:09 -0600 @lbutlr krem...@kreme.com wrote:
| # /usr/local/sbin/named -u bind -c /etc/namedb/named.conf \
| -t /var/named
|
| Yes, that works without reporting any errors, so the issue appears to be
| with /usr/local/etc/rc.d/named startup script.
Well, your first
On 31/03/2015 02:32, @lbutlr wrote:
Can you start the named process by hand -- the command line should be
something like:
# /usr/local/sbin/named -u bind -c /etc/namedb/named.conf \
-t /var/named
Yes, that works without reporting any errors, so the issue appears to
be with
On Mar 31, 2015, at 02:46, Mathieu Arnold m...@freebsd.org wrote:
+--On 30 mars 2015 19:32:09 -0600 @lbutlr krem...@kreme.com wrote:
| # /usr/local/sbin/named -u bind -c /etc/namedb/named.conf \
|-t /var/named
|
| Yes, that works without reporting any errors, so the issue appears to
On 03/30/15 00:35, @lbutlr wrote:
Downloaded and compiled bind-9.9.7 (FreeBSD 8.4-RELEASE) and it built fine
(./configure make make install).
On FreeBSD, building software out of the ports is definitely
recommended. It does the usual configure and make dance, but you also
get the benefit of
+--On 29 mars 2015 17:35:09 -0600 @lbutlr, krem...@kreme.com wrote:
| Downloaded and compiled bind-9.9.7 (FreeBSD 8.4-RELEASE) and it built
| fine (./configure make make install).
What does the port version not do that you need ?
| If I try to start named (service named start), it starts this
On Sun, 29 Mar 2015, INVALID_ADDRESS wrote:
named_conf=/etc/namedb/named.conf # Path to the configuration file
...
So I changed the path (in /etc/rc.conf) to /usr/local/sbin/named
But now I get:
$ /etc/rc.d/named start
Starting named.
/etc/rc.d/named: WARNING: failed to start named
+--On 30 mars 2015 16:46:36 +0200 Daniel Ryslink
daniel.rysl...@dialtelecom.cz wrote:
| In 8.4., the default chroot for BIND is /var/named, you might want to use
| that. Please not that in FreeBSD 10, BIND is removed from system and
| replaced with Unbound as the default resolver, and the chroot
Prefered procedure:
1) Install the ports collection via portsnap fetch and then portsnap
extract (or portsnap update if already installed)
2) Go to /usr/ports/dns/bind99 and type make install
Please note that after installing, you will have two versions of BIND on
your system:
- the
That's not true, it's just not enabled by default, because it is a
mess to
get *right* when migrating from {8,9} to 10.
On the contrary, see the FreeBSD 10 release notes:
https://www.freebsd.org/releases/10.0R/announce.html
Quote:
- Unbound has been imported to the base system as the local
+--On 30 mars 2015 19:12:30 +0200 Daniel Ryslink
daniel.rysl...@dialtelecom.cz wrote:
| That's not true, it's just not enabled by default, because it is a
| mess to
| get *right* when migrating from {8,9} to 10.
|
| On the contrary, see the FreeBSD 10 release notes:
|
|
On Mon, Mar 30, 2015 at 12:41 PM, Mathieu Arnold m...@freebsd.org wrote:
+--On 30 mars 2015 19:12:30 +0200 Daniel Ryslink
daniel.rysl...@dialtelecom.cz wrote:
| That's not true, it's just not enabled by default, because it is a
| mess to
| get *right* when migrating from {8,9} to 10.
On Mar 30, 2015, at 2:30 AM, Matthew Seaman m.sea...@infracaninophile.co.uk
wrote:
On 03/30/15 00:35, @lbutlr wrote:
Downloaded and compiled bind-9.9.7 (FreeBSD 8.4-RELEASE) and it built fine
(./configure make make install).
On FreeBSD, building software out of the ports is definitely
Downloaded and compiled bind-9.9.7 (FreeBSD 8.4-RELEASE) and it built fine
(./configure make make install).
If I try to start named (service named start), it starts this version instead
of the version in /usr/local/sbin
I found this in /etc/defaults/rc,conf:
named_enable=NO #
14 matches
Mail list logo
