Hinweis: Das Forum wird geschlossen! Neue Registrierungen sind nicht mehr möglich!

 Zurück zu Pro-Linux   Foren-Übersicht   FAQ     Suchen    Mitgliederliste
Dynamisches DNS klappt nicht. BIND9 streikt :-(((

 
Neuen Beitrag schreiben   Auf Beitrag antworten    Pro-Linux Foren-Übersicht -> Netzwerk
Vorheriges Thema anzeigen :: Nächstes Thema anzeigen  
Autor Nachricht
helldiver



Anmeldungsdatum: 16.08.2004
Beiträge: 1

BeitragVerfasst am: 16. Aug 2004 23:54   Titel: Dynamisches DNS klappt nicht. BIND9 streikt :-(((

mm ich hab mal versucht in meinem kleenen Test LAN einen Server mit DHCP und Bind 9 mit DDNS aufzusetzen. Ich hab mich da ziemlich genau an die DDNS Howto gehalten die bei Suse 9.0 dem Paket dhcp-server beiliegt. Nun denn als ich den Named neu starten wollte zickte der mit: "/etc/named2.keys:4: key 'DHCP_UPDATER': already exists" rum und wollte nicht mehr ;-( Ich hab euch hier mal meine dhcp.conf , named.conf reinkopiert, vielleicht findet ihr den Fehler. Wäre da echt froh für jede um Hilfe.

Schon mal danke im voraus.

Greetz Markus



DHCP.conf:
_____________________________________________
ddns-rev-domainname "home";
option root-path "/";
option subnet-mask 255.255.255.0;
ddns-updates on;
ddns-domainname "home";
option broadcast-address 192.168.0.255;
#
# Sample configuration file for ISC dhcpd
#

option domain-name "home";
option domain-name-servers 192.168.0.1;

default-lease-time 600;
max-lease-time 7200;

# if you do not use dynamical DNS updates:
#
ddns-update-style interim;
ignore client-updates;
include "/etc/named.keys";

# If this DHCP server is the official DHCP server for the local # network, the authoritative directive should be uncommented.
authoritative;

# Use this to send dhcp log messages to a different log file (you also # have to hack syslog.conf to complete the redirection). log-facility local7;

# No service will be given on this subnet, but declaring it helps the
# DHCP server to understand the network topology.


# This is a very basic subnet declaration.


# This declaration allows BOOTP clients to get dynamic addresses, # which we don't really recommend.



# Hosts which require special configuration options can be listed in
# host statements. If no address is specified, the address will be
# allocated dynamically (if possible), but the host-specific information # will still come from the host declaration.


# Fixed IP addresses can also be specified for hosts. These addresses
# should not also be listed as being available for dynamic assignment. # Hosts for which fixed IP addresses have been specified can boot using
# BOOTP or DHCP. Hosts for which no fixed address is specified can only
# be booted with DHCP, unless there is an address range on the subnet # to which a BOOTP client is connected which has the dynamic-bootp flag

# You can declare a class of clients and then do address allocation
# based on that. The example below shows a case where all clients
# in a certain class get addresses on the 10.17.224/24 subnet, and all # other clients get addresses on the 10.0.29/24 subnet.

class "foo" {
match if substring (option vendor-class-identifier, 0, 4) = "SUNW"; }

shared-network home {
ddns-updates on;
ddns-rev-domainname "home";
ddns-domainname "home";
subnet 192.168.0.0 netmask 255.255.255.0 {
ddns-updates on;
ddns-rev-domainname "home";
ddns-domainname "home";
range 192.168.0.2 192.168.0.16;
zone home. { primary 127.0.0.1; key DHCP_UPDATER; }
zone 192.168.0.in-addr.arpa. { primary 127.0.0.1; key DHCP_UPDATER; }
allow unknown-clients;
}



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 { 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 SuSEconfig.named. This includes # all files as configured in NAMED_CONF_INCLUDE_FILES from # /etc/sysconfig/named

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

zone "home" {
type master;
file "/var/lib/named/dyn/home.hosts";
allow-update { key DHCP_UPDATER; };
};

zone "0.168.192.in-addr.arpa" {
type master;
file "/var/lib/named/dyn/192.168.0.rev";
allow-update { key DHCP_UPDATER; };

};}
 
Benutzer-Profile anzeigen Private Nachricht senden

Glas Kugel
Gast





BeitragVerfasst am: 17. Aug 2004 0:19   Titel:

Du solltest uns schon verraten, was dort geschrieben steht!!!

include "/etc/named.keys";

/etc/named2.keys:4
 

Beiträge vom vorherigen Thema anzeigen:   
     Pro-Linux Foren-Übersicht -> Netzwerk Alle Zeiten sind GMT + 1 Stunde
Seite 1 von 1

 
Gehen Sie zu:  

Powered by phpBB © phpBB Group
pro_linux Theme © 2004 by Mandaxy