Roland Ehle schrieb am 15.10.05 10:41:54:
Hallo Bernd,
Am Samstag, den 15.10.2005, 00:32 +0200 schrieb Bernd Kloss:
ich habe mir vermutlich den Name/Bind9 zerschossen und finde den Fehler nicht.
Beim Booten des Clients kommt an der Stelle
NFS
mount: can't get adress from SERVER
/home liegt auf dem SERVER und kann natürlich nun nicht vom CLIENT erreicht werden.
PING CLIENT vom Server funktioniert
PING IP-DES-CLIENTS vom Server funktioniert
PING IP-DES-SERVERS vom Client funktioniert
Ein PING SERVER vom Client meldet unknown host
Quick and dirty Lösung für dieses Problem: auf dem Client in /etc/hosts
SERVER und dazugehörige IP eintragen. Ansonsten wäre es hilfreich, die
Datei named.conf des SERVER zu sehen, um weiter zu analysieren.
Gruß,
Roland
Hallo,
und erstmal danke für das Hilfsangebot.
Hier ist die named.conf:
# Copyright (c) 2001-2004 SuSE Linux AG, Nuernberg, Germany.
# All rights reserved.
#
# Author: Frank Bodammer, Lars Mueller
#
#neu: 13. Okt. 05
#
# /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/bind/sample-config.
#
# A description of all available options can be found in
# /usr/share/doc/packages/bind/misc/options.
options {
# The directory statement defines the name server's working directory
directory "/var/lib/named";
# Write dump and statistics file to the log subdirectory. The
# pathenames are relative to the chroot jail.
dump-file "/var/log/named_dump.db";
statistics-file "/var/log/named.stats";
# 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.
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/16;};
# 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;
include "/etc/named.d/forwarders.conf";
};
# To configure named's logging remove the leading '#' characters of the
# following examples.
#logging {
# # Log queries to a file limited to a size of 100 MB.
# channel query_logging {
# file "/var/log/named_querylog"
# versions 3 size 100M;
# print-time yes; // timestamp log entries
# };
# category queries {
# query_logging;
# };
#
# # Or log this kind alternatively to syslog.
# channel syslog_queries {
# syslog user;
# severity info;
# };
# category queries { syslog_queries; };
#
# # Log general name server errors to syslog.
# channel syslog_errors {
# syslog user;
# severity error;
# };
# category default { syslog_errors; };
#
# # Don't log lame server messages.
# 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";
};
# Include the meta include file generated by createNamedConfInclude. This
# includes all files as configured in NAMED_CONF_INCLUDE_FILES from
# /etc/sysconfig/named
include "/etc/named.conf.include";
# You can insert further zone records for your own domains below or create
# single files in /etc/named.d/ and add the file names to
# NAMED_CONF_INCLUDE_FILES.
# See /usr/share/doc/packages/bind/README.SUSE for more details.
zone "gym-anna.intra" in {
type master;
file "mydomain.file";
};
zone "0.0.168.192.in-addr.arpa" in {
type master;
file "mydomain.file.rev";
};
logging {
category default { log_syslog; };
channel log_syslog { syslog; };
};
Und hier die Hosts, gekürzt, aber die Struktur ist gleich:
# 05.09.2005
# ACHTUNG: in /var/lib/named muessen die Rechner auch noch in
# mydomain.files und mydomain.files.rev
# eingetragen werden und danach muss noch mit
# rcnamed restart
# der name-server neu gestartet werden
#
#
#
# hosts This file describes a number of hostname-to-address
# mappings for the TCP/IP subsystem. It is mostly
# used at boot time, when no name servers are running.
# On small systems, this file can be used instead of a
# "named" name server.
# Syntax:
#
# IP-Address Full-Qualified-Hostname Short-Hostname
#
127.0.0.1 localhost
# special IPv6 addresses
::1 localhost ipv6-localhost ipv6-loopback
fe00::0 ipv6-localnet
ff00::0 ipv6-mcastprefix
ff02::1 ipv6-allnodes
ff02::2 ipv6-allrouters
ff02::3 ipv6-allhosts
192.168.136.3 Pythia.gym-anna.intra Pythia
192.168.136.5 Switch.gym-anna.intra Switch
#192.168.136.6 Switch1.gym-anna.intra Switch1
192.168.136.11 Platz1.gym-anna.intra Platz1
192.168.136.12 Platz2.gym-anna.intra Platz2
192.168.136.13 Platz3.gym-anna.intra Platz3
.
.
.
192.168.136.251 Kunst4.gym-anna.intra Kunst4
10.0.1.1 mars.gym-anna.intra
192.168.136.1 mars.gym-anna.intra mars
Das ganze ist dann noch in der mydomain.files und ....rev drin
Ich sehe einfach den Fehler nicht.
Viele Grüße
Bernd
______________________________________________________________
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193
