myGully.com - Hilfe! (Debian)

Hey Leute,

Ich habe folgendes Problem:

Ich habe einen Debian Lenny Sever auf dem ein Router, ein DNS-Server und ein DHCP-Server läuft, jetzt soll des aber DDNS sein, also sprich der DHCP-Server soll seine Clients in den DNS-Server eintragen. Das Funktioniert aber nicht..

Meine config-files schauen wie folgt aus...

BIND9:

named.conf

Zitat:

// This is the primary configuration file for the BIND DNS server named.
//
// Please read /usr/share/doc/bind9/README.Debian.gz for information on the
// structure of BIND configuration files in Debian, *BEFORE* you customize
// this configuration file.
//
// If you are just adding zones, please do that in /etc/bind/named.conf.local

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

// prime the server with knowledge of the root servers
zone "." {
type hint;
file "/etc/bind/db.root";
};

// be authoritative for the localhost forward and reverse zones, and for
// broadcast zones as per RFC 1912

# key "rndc-key" {
# algorithm hmac-md5;
# secret "gnHoNI5uRYmts7B9BPe03w==";
# };

# options {
# directory "/etc/bind";
# allow-transfer { "ilonanetz"; };
# allow-query { "ilonanetz"; };
# listen-on port 53 {"home"; };
# auth-nxdomain no; #conform to RFC1035
#
# forwarders {
# 192.168.0.213;
# 192.198.0.213;
# };
# };

zone "localhost" {
type master;
file "/etc/bind/db.local";
};

zone "127.in-addr.arpa" {
type master;
file "/etc/bind/db.127";
};

zone "0.in-addr.arpa" {
type master;
file "/etc/bind/db.0";
};

zone "255.in-addr.arpa" {
type master;
file "/etc/bind/db.255";
};

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

controls {
inet 127.0.0.1 allow {localhost; } keys { "rndc-key"; };
};

named.conf.local

Zitat:

zone "ilonanetz." {
type master;
file "/etc/bind/db.ilonanetz";
allow-update { key "rndc-key"; };
};

zone 32.172.in-addr.arpa {
type master;
file "/etc/bind/db.172.32";
allow-update { key "rndc-key"; };
notify yes;
};

include "/etc/bind/rndc.key";
controls {
inet 127.0.0.1 port 53
allow { 127.0.0.1; } keys {"rndc-key"; };
};

// Do any local configuration here
//

// Consider adding the 1918 zones here, if they are not used in your
// organization
//include "/etc/bind/zones.rfc1918";

DHCPD:

dhcpd.conf

Zitat:

# /*
# Sample configuration file for ISC dhcpd for Debian
#
# $Id: dhcpd.conf,v 1.1.1.1 2002/05/21 00:07:44 peloy Exp $
#

# The ddns-updates-style parameter controls whether or not the server will
# attempt to do a DNS update when a lease is confirmed. We default to the
# behavior of the version 2 packages ('none', since DHCP v2 didn't
# have support for DDNS
# // ddns-update-style none;

# option definitions common to all supported networks...
# // option domain-name "example.org";
# // option domain-name-servers ns1.example.org, ns2.example.org;

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

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

# subnet 10.152.187.0 netmask 255.255.255.0 {
# }

# This is a very basic subnet declaration.

# subnet 10.254.239.0 netmask 255.255.255.224 {
# range 10.254.239.10 10.254.239.20;
# option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org;
# }

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

# subnet 10.254.239.32 netmask 255.255.255.224 {
# range dynamic-bootp 10.254.239.40 10.254.239.60;
# option broadcast-address 10.254.239.31;
# option routers rtr-239-32-1.example.org;
# }

# A slightly different configuration for an internal subnet.
# subnet 10.5.5.0 netmask 255.255.255.224 {
# range 10.5.5.26 10.5.5.30;
# option domain-name-servers ns1.internal.example.org;
# option domain-name "internal.example.org";
# option routers 10.5.5.1;
# option broadcast-address 10.5.5.31;
# default-lease-time 600;
# max-lease-time 7200;
# }

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

# host passacaglia {
# hardware ethernet 0:0:c0:5d:bd:95;
# filename "vmunix.passacaglia";
# server-name "toccata.fugue.com";
# }

# 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
# set.
# host fantasia {
# hardware ethernet 08:00:07:26:c0:a5;
# fixed-address fantasia.fugue.com;
# }

# 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 224-29 {
# subnet 10.17.224.0 netmask 255.255.255.0 {
# option routers rtr-224.example.org;
# }
# subnet 10.0.29.0 netmask 255.255.255.0 {
# option routers rtr-29.example.org;
# }
# pool {
# allow members of "foo";
# range 10.17.224.10 10.17.224.250;
# }
# pool {
# deny members of "foo";
# range 10.0.29.10 10.0.29.230;
# }
# }

# log-facility local17;
# */

subnet 172.32.0.0 netmask 255.255.0.0
{
option domain-name "ilonanetz";
option domain-name-servers 172.32.0.1;
option routers 172.32.0.1;
option broadcast-address 172.32.0.255;
option subnet-mask 255.255.0.0;
default-lease-time 172800;
max-lease-time 604800;
range 172.32.0.3 172.32.0.253;
}

authoritative;
include "/var/chroot/bind9/etc/bind/rndc.key";
ddns-update-style interim;
ddns-updates on;