Probleme beim DNS einrichten

[kelnoky]

Hi,

ich wollte nun einen DNS-Server unter OpenSuSe 11.1 einrichten. Hab auch ein schönes HowTo gefunden, aber das bezieht sich nur auf 10.2. Dennoch gehts eigentlich. Das Problem ist nun, wenn ich fertig bin und auf "Beenden" klicke, geht YaST eine Checkliste durch und bei "DNS-Dienst anpassen" erscheint die Fehlermeldung:

Fehler

Error occured while starting service named.2

Error: [1m

Warning: (B [mFile /etc/named.conf.include not found. Skipping.

/etc/named.conf:128:open: /etc/named.conf.include: file not found

Tja, was heißt das denn nun und wie kann man den Fehler beheben?

Scheint, als hat er eine Datei nicht gefunden. Muss ich die selbst anlegen? Was muss denn dann da rein? Oder wie löst man das?

lg

kelnoky

// Zusatz:

Jetzt hab ich ein weiteres Problem: Ich hatte im DHCP-Server das Netzwerk 192.168.2.0 angegeben und wollte das nun im Nachhinein ändern auf 192.168.0.0! Das geht aber nicht mehr die Einstellungen, welches Netzwerk, Subnetzmaske usw. grau unterlegt und nicht änderbar. Im Expertenmodus kann ich zwar das Netz ändern, aber sobald ich da auf "Beenden" klicke, zeigt er die gleiche Fehlermeldung wie der DNS :/

Kann ich die DHCP-Einstellungen nochma komplett neu machen? Vllt behebt sich ja dann auch der DNS-Fehler, dort hab ich nämlich schon das 192.168.0.0-Netz verwendet und auch den DHCP dort eingetragen

jetzt funktioniert gar nichts mehr -.- ich kann nichtmal mehr den DHCP ändern...

Bearbeitet 29. Januar 2009 von kelnoky

[lupo49]

Wenn der Teil in /etc/named.conf in Ordnung ist, dann kommentier mal das "include /etc/named.conf.include" aus.

Poste mal deine /etc/named.conf.

[kelnoky]

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

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

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

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

};

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

zone "0.168.192.in-addr.arpa" in {

allow-transfer { none; };

file "master/0.168.192.in-addr.arpa";

type master;

};

logging {

category default { log_syslog; };

channel log_syslog { syslog; };

};

zone "project.test" in {

allow-transfer { none; };

file "master/project.testX";

type master;

};

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

sobald ich den DHCP starten will, kommt nur noch oben genannter Fehler. Man muss doch irgendwie die config löschen können?

Bearbeitet 29. Januar 2009 von kelnoky

[lupo49]

include "/etc/named.conf.include";

Mach vor die Zeile mal ein #.

Was steht in /etc/sysconfig/named?

[kelnoky]

## Path: Network/DNS/Name Server

## Description: Names server settings

## Type: yesno

## Default: yes

## ServiceRestart: lwresd,named

#

# Shall the DNS server 'named' or the LightWeight RESolver Daemon, lwresd run

# in the chroot jail /var/lib/named/?

#

# Each time you start one of the daemons with the init script, /etc/named.conf,

# /etc/named.conf.include, /etc/rndc.key, and all files listed in

# NAMED_CONF_INCLUDE_FILES will be copied relative to /var/lib/named/.

#

# The pid file will be in /var/lib/named/var/run/named/ and named named.pid

# or lwresd.pid.

#

NAMED_RUN_CHROOTED="yes"

## Type: string

## Default: ""

## ServiceRestart: lwresd,named

#

# Additional arguments when starting the name daemon with the init script

# /etc/init.d/named or rcnamed.

#

# For example "-n 2" to use two CPUs if named is unable to determine the

# number of available CPUs.

#

# See man 8 named for all available commandline options.

#

# "-t /var/lib/named/var" is added if NAMED_RUN_CHROOTED is set to yes.

#

# "-u named" is used in any case by the init script to run the named daemon as

# user 'named' after completing privileged operations.

#

NAMED_ARGS=""

## Type: string

## Default: ""

## ServiceReload: named

#

# All mentioned config files will be copied relativ to /var/lib/named/, when

# 'named' is started in the chroot jail.

#

# /etc/named.conf and /etc/rndc.key are always copied. Also all files from

# include statements in named.conf.

#

# Filenames can be relative to /etc/named.d/.

#

# Please take care of the order if one file needs a setting of another.

#

# Example: "/etc/named-dhcpd.key ldap.dump rndc-access.conf"

#

NAMED_CONF_INCLUDE_FILES=""

## Type: string

## Default: "createNamedConfInclude"

## ServiceReload: named

#

# Programms to be executed each time the DNS server 'named' is started or

# reloaded.

#

# Filenames can be relative to /usr/share/bind/.

#

NAMED_INITIALIZE_SCRIPTS="createNamedConfInclude"

[kelnoky]

hallo,

hab das Problem gefunden - das falsche Interface war eingestellt, dadurch ließ sich auch nicht der Netzwerkbereich ändern.

Die Server hab ich abgeschaltet, DHCP neu konfiguriert und und geht wieder alles und lässt sich auch speichern. Keine Fehlermeldung mehr.

Vielen Dank für die schnelle und freundliche Hilfe

[SaJu]

Hallo,

ich habe das gleiche Problem.

Die Server hab ich abgeschaltet, DHCP neu konfiguriert und und geht wieder alles und lässt sich auch speichern. Keine Fehlermeldung mehr.

Das habe ich schon versucht.

Mit "/etc/init.d/dhcpd stop" konnte ich den DHCP-Server stoppen.

Beim DNS-Server gibt es Probleme:

Wenn ich "/etc/init.d/named status" eingebe kommt dead.

Allerdings hat vorher der DHCP-Server die gleiche Fehlermeldung gebracht:

Fehler

Error occured while starting service named.2

Error: [1m

Warning: (B [mFile /etc/named.conf.include not found. Skipping.

/etc/named.conf:128:open: /etc/named.conf.include: file not found

Wenn ich dann den DNS-Server mit "/etc/init.d/named stop" stoppen will, kommt:

Shutting down name server BIND - Warning: named notdonerunning!

Das "done" erscheint in der Shell so grün.

Was kann ich machen?

[SaJu]

Bei mir ist die Datei "/etc/named.conf"-Datei so:

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

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

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

# 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 "localhost127.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";

logging {

category default { log_syslog; };

channel log_syslog { syslog; };

};

zone "schulung.de" in {

allow-transfer { localhost; };

file "master/schulung.de";

type master;

};

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

Beim Server soll es die Domain Schulung.de geben.

Wie bei der Fehlermeldung schon gesagt: /etc/init.d/named.conf.include existiert nicht und wird nicht erstellt.

Bearbeitet 8. Oktober 2010 von SaJu