Bind9 vil ikke køre efter rettelse af named.conf

hvad siger dine log-filer (/var/log/messages) ?

kører du bind om en bestemt bruger og kan der være noget fnidder med rettighederne ?

Jeg er kun logget på som root, log:

Feb  4 11:05:26 linux3 named[4991]: none:0: open: /etc/named.conf: permission denied
Feb  4 11:05:26 linux3 named[4991]: loading configuration: permission denied
Feb  4 11:05:26 linux3 named[4991]: exiting (due to fatal error)

prøv evt at lave en

chmod 644 /etc/named.conf

mit gæt er at /etc/named.conf ejes af root og bind kører som brugen named - eller noget i den retning.

Noget har det ændret at køre chmod 644, men servicen kan dog stadig ikke startes

Feb  4 11:46:51 linux3 named[5255]: /etc/named.conf:105: unexpected end of input
Feb  4 11:46:51 linux3 named[5255]: loading configuration: unexpected end of input
Feb  4 11:46:51 linux3 named[5255]: exiting (due to fatal error)

prøv evt lige at smide rcnamed her

det kan være en manglende { eller ; så hvis du kan lægge named.conf her også så er det lidt nemmere ...

du kan evt også lige prøve at teste det selv via named -d 2 og se om den giver noget.

den mener jo at i linie 105 stopper den så du kan evt se hvad der står deromkring...

named.conf:

# Copyright (c) 2001-2003 SuSE Linux AG, Nuernberg, Germany
#
# Author: Frank Bodammer, Lars Mueller <lmuelle@suse.de>
#
# /etc/named.conf
#
# This is a sample configuration file for the name server BIND 9.
# It works as a caching only name server without modification.
#
# A sample configuration for setting up your own domain can be
# found in /usr/share/doc/packages/bind9/sample-config.
#
# A description of all available options can be found in
# /usr/share/doc/packages/bind9/misc/options.

options {

    # The directory statement defines the name server's
    # working directory

    directory "/var/lib/named";

    # The forwarders record contains a list of servers to
    # which queries should be forwarded. Enable this line and
    # modify the IP-address to your provider's name server.
    # Up to three servers may be listed.

    #forwarders { 10.11.12.13; 10.11.12.14; };

    # Enable the next entry to prefer usage of the name
    # server declared in the forwarders section.

    #forward first;

    # The listen-on record contains a list of local network
    # interfaces to listen on. Optionally the port can be
    # specified. Default is to listen on all interfaces found
    # on your system. The default port is 53.

    #listen-on port 53 { 127.0.0.1; };

    # The listen-on-v6 record enables or disables listening
    # on IPV6 interfaces. Allowed values are 'any' and 'none'
    # or a list of addresses. IPv6 can only be used with
    # kernel 2.4 in this release.

    listen-on-v6 { any; };

    # The next three statements may be needed if a firewall
    # stands between the local server and the internet.

    #query-source address * port 53;
    #transfer-source * port 53;
    #notify-source * port 53;

    # The allow-query record contains a list of networks or
    # IP-addresses to accept and deny queries from. The
    # default is to allow queries from all hosts.

    #allow-query { 127.0.0.1; };

    # If notify is set to yes (default), notify messages are
    # sent to other name servers when the the zone data is
    # changed. Instead of setting a global 'notify' statement
    # in the 'options' section, a separate 'notify' can be
    # added to each zone definition.

    notify no;
};

# Remove the leading '#' characters if you want a log of the queries send to
# your name server. The log file size is limited to 100 MB.
#logging {
#    channel query_logging {
#        file "/var/log/named_querylog"
#            versions 3 size 100M;
#        print-time yes;            // timestamp log entries
#    };
#    category queries {
#        query_logging;
#    };
#    category lame-servers { null; };
#};

# The following zone definitions don't need any modification.
# The first one is the definition of the root name servers.
# The second one defines localhost while the third defines the reverse lookup
# for localhost.

zone "." in {
    type hint;
    file "root.hint";
};

zone "localhost" in {
    type master;
    file "localhost.zone";
};

zone "0.0.127.in-addr.arpa" in {
    type master;
    file "127.0.0.zone";
};

# You can insert further zone records for your own domains below.

rcnamed:

#! /bin/sh
# Copyright (c) 1995-2003 SuSE Linux AG, Nuernberg, Germany
#
# init.d/named
#
### BEGIN INIT INFO
# Provides:      named
# Required-Start: $network $remote_fs $syslog
# Required-Stop:
# Default-Start:  3 5
# Default-Stop:
# Description:    Starts internet domain name server (DNS)
### END INIT INFO

. /etc/rc.status
rc_reset

SYSCONFIG_FILE="/etc/sysconfig/named"

for configfile in ${SYSCONFIG_FILE} /etc/named.conf; do
    if [ ! -f ${configfile} ]; then
        echo -n "Name server configuration file ${configfile} does not exist."
        # Tell the user this has skipped
        rc_status -s
        exit 6
    fi
done
. /etc/sysconfig/named

test "${NAMED_RUN_CHROOTED}" = "yes" && \
    CHROOT_PREFIX="/var/lib/named" || \
    CHROOT_PREFIX=""

NAMED_ARGS=""
NAMED_BIN="/usr/sbin/named"
NAMED_PID="${CHROOT_PREFIX}/var/run/named/named.pid"
NAMED_CONF="/etc/named.conf"

if [ ! -x ${NAMED_BIN} ] ; then
    echo -n "Name server not installed!"
    # Tell the user this has skipped
    rc_status -s
    exit 5
fi

function prepare_chroot
{
    for configfile in /etc/{localtime,named.conf,rndc.key} ${NAMED_CONF_INCLUDE_FILES}; do
        test -d ${CHROOT_PREFIX}/${configfile%/*} || mkdir -p ${CHROOT_PREFIX}/${configfile%/*}
        cp -a ${configfile} ${CHROOT_PREFIX}/${configfile%/*}
    done
    NAMED_ARGS="-t ${CHROOT_PREFIX}"
}

export PATH="/sbin:/usr/sbin:/bin:/usr/bin"

case "$1" in
    start)
    echo -n "Starting name server BIND 9 "
    checkproc -p ${NAMED_PID} ${NAMED_BIN}
    case $? in
        0) echo -n "- Warning: named already running!" ;;
        1) echo -n "- Warning: ${NAMED_PID} exists!" ;;
    esac
    test "${NAMED_RUN_CHROOTED}" = "yes" && prepare_chroot
    startproc -p ${NAMED_PID} ${NAMED_BIN} ${NAMED_ARGS} -u named
    rc_status -v
    ;;
    stop)
    echo -n "Shutting down name server BIND 9 "
    checkproc -p ${NAMED_PID} ${NAMED_BIN} || echo -n "- Warning: named not running!"
    killproc -p ${NAMED_PID} -TERM ${NAMED_BIN}
    rc_status -v
    ;;
    try-restart)
    $0 status >/dev/null && $0 restart
    rc_status
    ;;
    restart)
    $0 stop
    $0 start
    rc_status
    ;;
    force-reload)
    $0 reload
    rc_status
    ;;
    reload)
    echo -n "Reloading name server BIND 9 "
    checkproc -p ${NAMED_PID} ${NAMED_BIN} || echo -n "- Warning: named not running!"
    test "${NAMED_RUN_CHROOTED}" = "yes" && prepare_chroot
    killproc -p ${NAMED_PID} -HUP ${NAMED_BIN}
    rc_status -v
    ;;
    status)
    echo -n "Checking for nameserver BIND 9 "
    checkproc -p ${NAMED_PID} ${NAMED_BIN}
    rc_status -v
    ;;
    probe)
    test ${NAMED_CONF} -nt ${NAMED_PID} && echo reload
    ;;
    *)
    echo "Usage: $0 {start|stop|status|try-restart|restart|force-reload|reload|probe}"
    exit 1
    ;;
esac
rc_exit

har du haft den ovre i dos ? og er der en newline i sidste linie ?

den startede godt nok op på min maskine, nemlig. En ting som du måske bør udkommentere er listen-on-v6 { any; }; medmindre du har en god grund til at have den der

kører du den chrootet ?

umiddelbart efter at have udkommenteret "listen-on-v6" virker det. Lidt mystisk dog specielt nu hvor jeg prøvede, at sætte en anden PC op med samme konfiguration, denne virker uden at "listen-on-v6" er udkommenteret!? det er vist ikke alt man skal forstå!

husk at lægge et svar for points ...og jeg takker for hjælpen

lukkes