PDA

Archiv verlassen und diese Seite im Standarddesign anzeigen : DNS Client findet DNS Server (named) anscheinend nicht



thehenny
28.11.04, 22:36
Hallo,

sonst habe ich hier alles mit Hilfe der Suchefunktion gefunden, falls ich mal Probleme hatte ;) . Nur nun habe ich leider keinen passenden Thread gefunden....

Also mein Problem:

Ich habe auf dem Rechner "server" einen DNS-Server (named) laufen, welcher dort auch super funktioniert. D.h. wenn ich dort z.b. "host hennyn" eingebe, zeigt er mir auch die richtig zugeordnete IP.
Nun habe ich aber auf dem Client "hennyn" den Nameserver eingetragen, doch dieser findet leider gar nichts....



henny@hennyn:~> host henny
Host henny not found: 3(NXDOMAIN)


geht das gleich wenn ich versuche ihn anzupingen....

Hier mal meine config:




#/etc/named.conf
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";

# 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 { 212.185.253.70; 168.95.1.1; };

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

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

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

zone "hen" in {

type master;
notify no ;
file "hen.zone";
};

zone "7.168.192.in-addr.arpa"
{
type master;
notify no;
file "192.168.7.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";




Ich hoffe ihr könnt mir helfen....

fg
henny

P.S: Auf dem Server und auch auf dem Client laufen SUSE 9.2

mkahle
29.11.04, 06:17
wie sehen auf den beiden Rechnern die Dateien /etc/resolv.conf aus? Ggf. sind auch noch /etc/hosts und /etc/nsswitch.conf von Interesse.

thehenny
29.11.04, 07:34
Hi mkahle,

Client:

resolv.conf:


nameserver 192.168.7.10
search hen


hosts:


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


nsswitch.conf:


passwd: compat
group: compat

hosts: files lwres dns
networks: files dns

services: files
protocols: files
rpc: files
ethers: files
netmasks: files
netgroup: files
publickey: files

bootparams: files
automount: files nis
aliases: files



Server:

resolv.conf:


search hen
nameserver 127.0.0.1


hosts:


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


nsswitch.conf:


passwd: compat
group: compat

hosts: files lwres dns
networks: files dns

services: files
protocols: files
rpc: files
ethers: files
netmasks: files
netgroup: files
publickey: files

bootparams: files
automount: files nis
aliases: files



ich hoffe das hilft weiter :o

thehenny
29.11.04, 12:56
Das Problem hat sich erledigt. Ich weiß nun wirklich nicht was verstellt habe, bzw ob ich überhaupt was verstellt habe, aber ich komme grad von der Arbeit (Zivi :cool: ) und mach den Server && Client an und alles läuft prima :rolleyes:

Naja, trotzdem vielen Dank für deine schnelle Antwort!!!!!