Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 1 Feb 2003 10:12:29 +0000
From:      Matthew Seaman <>
To:        freebsd-questions@FreeBSD.ORG
Subject:   Re: BIND 9.2.2rc1 installation confirmation?
Message-ID:  <20030201101229.GA84798@happy-idiot-talk.infracaninophi>
In-Reply-To: <000201c2c81a$6551f4d0$ee97fea9@james>
References:  <000201c2c81a$6551f4d0$ee97fea9@james>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Wed, Jan 29, 2003 at 11:45:17PM -0500, Jamie wrote:

> It required OpenSSL 0.9e or higher which I was able to get to install
> with "make; make install". Then I continued with another attempt at
> BIND. I finally finished with the installation but now I can't seem to
> find a way to confirm that BIND is properly installed and running. When
> I start it, it does not report the version as the docs seem to indicate
> it should. Also, running Top doesn't show anything like BIND or named or
> anything else that reasonably indicates that I've succeeded in starting
> it. Maybe I'm not starting it correctly. Can someone please provide me
> with the official syntax?

The process you want to see is 'named'.  It won't start up
automatically when you install the Bind 9 port -- you'll have to start
it yourself from the command line, and arrange for it to be restarted
automatically on reboot.

To start bind by hand (as root):

    # /usr/local/sbin/named -c /etc/named/named.conf -u bind

To see if it's running, as well as checking in the process table:

    % ps -axwww | grep named 
      100  ??  Is     0:40.24 /usr/local/sbin/named -c /etc/namedb/named.conf -u bind

you can check for processes listening on port 53:

    % sockstat | grep :53
    bind     named      100    4 udp4        *:*
    bind     named      100    5 tcp4        *:*
    bind     named      100    6 udp4          *:*
    bind     named      100    7 tcp4          *:*


    % netstat -an | grep '\.53'
    tcp4       0      0           *.*                    LISTEN
    tcp4       0      0         *.*                    LISTEN
    udp4       0      0           *.*
    udp4       0      0         *.*

Bind 9 is fairly picky about the syntax of it's configuration and zone
files.  If it finds a problem it will generally log an explanation to
/var/log/messages and then silently quit.  You'll need to make sure
that you have corrected any errors before it will start properly.  A
particularly problematic thing is the $TTL record that seems to be
required in all zone files nowadays.

Another gotcha that may catch you on FreeBSD is that Bind 9 doesn't
understand the '-g' flag as used by default with the system supplied
Bind 8.  You'll need something like this in /etc/rc.conf in order to
startup Bind 9 automatically on boot up:

    named_flags="-c /etc/namedb/named.conf -u bind"



Dr Matthew J Seaman MA, D.Phil.                       26 The Paddocks
                                                      Savill Way
PGP:         Marlow
Tel: +44 1628 476614                                  Bucks., SL7 1TH UK

To Unsubscribe: send mail to
with "unsubscribe freebsd-questions" in the body of the message

Want to link to this message? Use this URL: <>