bind: query (cache) denied

[krischan2000]

Hi,

hatte heute endlich mal meinen bind zum laufen bekommen, danach aber wahrscheinlich irgendwas vergeigt.

Bei ner Anfrage eines Clients kommt nur folgende Fehlermeldung:

Mar 1 17:56:04 krischan named[21366]: client ::ffff:192.168.0.3#1069: query (cache) denied

Hab schon im Forum, gesucht aber nicht wirklich was gefunden was mir helfen könnte.

bind startet so:



Mar 1 17:56:00 krischan named[21364]: starting BIND 9.2.2 -t /var/lib/named -u named
Mar 1 17:56:00 krischan named[21364]: using 1 CPU
Mar 1 17:56:00 krischan named[21366]: loading configuration from '/etc/named.conf'
Mar 1 17:56:00 krischan named[21366]: listening on IPv6 interfaces, port 53
Mar 1 17:56:00 krischan named[21366]: listening on IPv4 interface lo, 127.0.0.1#53
Mar 1 17:56:00 krischan named[21366]: binding TCP socket: address in use
Mar 1 17:56:00 krischan named[21366]: command channel listening on 127.0.0.1#953
Mar 1 17:56:00 krischan named[21366]: command channel listening on ::1#953
Mar 1 17:56:00 krischan named[21366]: 127.0.0.zone:10: file does not end with newline
Mar 1 17:56:00 krischan named[21366]: zone 0.0.127.in-addr.arpa/IN: has no NS records
Mar 1 17:56:00 krischan named[21366]: localhost.zone:11: file does not end with newline
Mar 1 17:56:00 krischan named[21366]: zone localhost/IN: has no NS records
Mar 1 17:56:00 krischan named[21366]: running


Als es funktionierte wars eigentlich genauso.. :(

/etc/named.conf:



# Copyright (c) 2001 SuSE GmbH Nuernberg, Germany
#
# Author: Frank Bodammer
#
# /etc/named.conf
#
# This is a sample configuration file for the name server BIND9.
# 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 {145.253.2.81; 145.253.2.196;};

# 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; 192.168.0.3;};

# 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; 192.168.0.0/24;};



# 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.
cleaning-interval 120;
notify no;
};

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

# localhost => 127.0.0.1
zone "localhost" in {
type master;
file "localhost.zone";
};

# 127.0.0.1 => localhost
zone "0.0.127.in-addr.arpa" in {
type master;
file "127.0.0.zone";
};

# Root Nameserver
zone "." in {
type hint;
file "root.hint";
};


Es steht ja aber da: allow-query {127.0.0.1; 192.168.0.0/24;}; trotzdem funktioert es nicht..

hat jemand ne idee?

thx schonmal

[Liberace]

Mit welcher IP Adresse greifst du auf den Bind zu, oder laeuft er lokal?

[krischan2000]

also der bind läuft auf meinem rechner der gleichzeit router ist.. ip 192.168.0.1
die clients hab dann 192.168.0.1/2/3

[Liberace]

Und wieso lauscht denn Bind auf 192.168.0.3? Und wieso haben Client und Router die gleiche IP?

[krischan2000]

erm nö, mein rechner hat die inet verbindung, routet, ist dhcp server und darauf läuft auch der bind (als cache).. ist eben der server. Die clients hab dann die ips 2 und 3.. net 1 , sry das war nen schreibfehler.. :)

Wenn eben nen Client ne anfrage ans netz schickt wird die eben angelehnt mit eben der Begründung. DHCP funktionert alles...

[Liberace]

Wenn Bind auf 192.168.0.1 laeuft, was hat denn dies zu bedeuten?

listen-on port 53 { 127.0.0.1; 192.168.0.3;};