bind will nicht :(

megamimi

megamimi

Nörgler vom Dienst
Also mein bind will keine namen auflösen.

Das steht in /var/log/messages:

master zone "localhost" (IN) loaded (serial 42)
Mar 17 07:03:13 linux named[3744]: master zone "0.0.127.in-addr.arpa" (IN) loaded (serial 42)
Mar 17 07:03:13 linux named[3744]: hint zone "" (IN) loaded (serial 0)
Mar 17 07:03:13 linux named[3744]: listening on [127.0.0.1].53 (lo)
Mar 17 07:03:13 linux named[3744]: listening on [192.168.0.1].53 (eth0)
Mar 17 07:03:13 linux named[3744]: Forwarding source address is [0.0.0.0].53
Mar 17 07:03:13 linux named[3745]: group = named
Mar 17 07:03:13 linux named[3745]: user = named
Mar 17 07:03:13 linux named[3745]: Ready to answer queries.
Mar 17 07:03:13 linux named[3745]: sysquery: sendto([194.25.2.129].53): Operation not permitted

und das hier ist meine named.conf:
# Copyright (c) 2001 SuSE GmbH Nuernberg, Germany
#
# Author: Frank Bodammer <feedback@suse.de>
#
# /etc/named.conf
#
# This is a sample configuration file for the name server BIND8.
# 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/bind8/sample-config.
#
# A description of all available options can be found in
# /usr/share/doc/packages/bind8/html/options.html

options {

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

directory "/var/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 { 217.5.99.105; 194.25.2.129; };

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

forward only;

# 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.1; };

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

query-source address * 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 { 192.168.0.0; };

# The cleaning-interval statement defines the time interval
# in minutes for periodic cleaning. Default is 60 minutes.
# By default, all actions are logged to /var/log/messages.

cleaning-interval 120;

# Name server statistics will be logged to /var/log/messages
# every <statistics-interval> minutes. Default is 60 minutes.
# A value of 0 disables this feature.

statistics-interval 0;

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

# 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.

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

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

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

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

Leider hab ich gar keine Idee wo ich den Hebel ansetzen muss.
Das ganze soll am Ende dann als caching server für mein lan rennen.

danke,mimi
 
Versuchs mal mit...

Ich kann dir den dnscache von Bernstein empfehlen!! Das ist ein kleiner und sicherer dns server!! Liecht zu konfigurieren und schnell zu installieren!!

Infos bei D. J. Bernstein

Gruß

Daniel
 
hi...

Ich würde es gerne mit BIND versuchen, wenn das möglich ist - kann ja nicht sein das der mit mir partout nicht will (andere ham ihn ja auch schon zum laufen gebracht... ;) )
Danke trotzdem, wenn ich an meinem BIND- Projekt scheitere weiche ich auf deinen Tipp aus:)
 
Schau mal nach meiner Anleitung die ich zum Thread "Gateway einrichten" geschrieben habe, dort habe ich eine gut funktionierende bind konfiguration hinterlassen.
 

Ähnliche Themen

Nginx als Reverse Proxy für Nextcloud und Emby

Zugriff Ubuntu 16.04. auf Freigabe 18.04. LTS nicht möglich

Email via script via Exchange Server (SASL)

ip6tables Problem

Adressvergabe in anderen Subnets

Zurück
Oben