[Einleitung]
Da wir im Januar nee LAN veranstalten wollte ich nen kleinen Server für die grundlegenden Netzwerkdienste aufsetzen, also dhcp und dns... Wie in der Sonderausgabe Netzwerk des Linuxmagazins beschrieben habe ich meine beiden Services so konfiguriert.[/Einleitung]
DHCPD funktioniert auch (ist dhcp3-server) und Bind9 sagt auch erstmal nichts weiteres beim start. Trotzdem funktioniert das "updaten" der DHCP verteilten adressen nicht. wäre toll wenn ihr euch mal die Konfigurationsdateien und die Log-Ausgabe ansehen könnte, denn ich komme partou nicht weiter ( und die suche auf diesem Board hat überhaupt erst hierzu geführt.)
also.. hier:
/etc/dhcp3/dhcpd.conf hat geschrieben: # option definitions common to all supported networks...
option domain-name-servers lansev;
option routers lansev;
option netbios-name-servers lansev;
option netbios-dd-server lansev;
option netbios-node-type 8;
update-static-leases true;
ignore client-updates;
authoritative;
default-lease-time 86400;
max-lease-time 2592000;
ddns-update-style interim;
ddns-domainname "intranet";
ddns-updates on;
zone intranet. {
primary 127.0.0.1;
}
zone 168.192.in-addr.arpa.{
primary 127.0.0.1;
}
# Alle
# Subnet 20
subnet 192.168.20.0 netmask 255.255.255.0 {
range 192.168.20.10 192.168.20.239;
range dynamic-bootp 192.168.20.240 192.168.20.250;
option broadcast-address 192.168.20.255;
option routers 192.168.20.1;
option subnet-mask 255.255.255.0;
option domain-name-servers 192.168.20.1;
option host-name = concat("mimas", binary-to-ascii(10,8,"",substring(leased-address,3,1)));
}
# Subnet 21
subnet 192.168.21.0 netmask 255.255.255.0 {
range 192.168.21.10 192.168.21.239;
range dynamic-bootp 192.168.21.240 192.168.21.250;
option broadcast-address 192.168.21.255;
option routers 192.168.21.1;
option subnet-mask 255.255.255.0;
option domain-name-servers 192.168.21.1;
option host-name = concat("dione", binary-to-ascii(10,8,"",substring(leased-address,3,1)));
}
# Subnet 22
subnet 192.168.22.0 netmask 255.255.255.0 {
range 192.168.22.10 192.168.22.239;
range dynamic-bootp 192.168.22.240 192.168.22.250;
option broadcast-address 192.168.22.255;
option routers 192.168.22.1;
option subnet-mask 255.255.255.0;
option domain-name-servers 192.168.22.1;
option host-name = concat("rhea", binary-to-ascii(10,8,"",substring(leased-address,3,1)));
}
# Subnet 23
subnet 192.168.23.0 netmask 255.255.255.0 {
range 192.168.23.10 192.168.23.239;
range dynamic-bootp 192.168.23.240 192.168.23.250;
option broadcast-address 192.168.23.255;
option routers 192.168.23.1;
option subnet-mask 255.255.255.0;
option domain-name-servers 192.168.23.1;
option host-name = concat("tethys", binary-to-ascii(10,8,"",substring(leased-address,3,1)));
}
# Subnet 24
subnet 192.168.24.0 netmask 255.255.255.0 {
range 192.168.24.10 192.168.24.239;
range dynamic-bootp 192.168.24.240 192.168.24.250;
option broadcast-address 192.168.24.255;
option routers 192.168.24.1;
option subnet-mask 255.255.255.0;
option domain-name-servers 192.168.24.1;
option host-name = concat("lapetus", binary-to-ascii(10,8,"",substring(leased-address,3,1)));
}
# Subnet 25
subnet 192.168.25.0 netmask 255.255.255.0 {
range 192.168.25.10 192.168.25.239;
range dynamic-bootp 192.168.25.240 192.168.25.250;
option broadcast-address 192.168.25.255;
option routers 192.168.25.1;
option subnet-mask 255.255.255.0;
option domain-name-servers 192.168.25.1;
option host-name = concat("titan", binary-to-ascii(10,8,"",substring(leased-address,3,1)));
}
/etc/bind/named.conf hat geschrieben:
include "/etc/bind/named.conf.options";
zone "." {
type hint;
file "/etc/bind/db.root";
};
zone "localhost" {
type master;
file "/etc/bind/db.local";
};
zone "168.192.in-addr.arpa" {
type master;
file "/etc/bind/db.168.192";
allow-update{127.0.0.1;};
};
zone "intranet" {
type master;
file "/etc/bind/db.intranet";
allow-update{127.0.0.1;};
};
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";
logging {
channel update_debug {
file "/var/log/dns_update.log";
severity debug 3;
print-category yes;
print-severity yes;
print-time yes;
};
channel security_info {
file "/var/log/named.info";
severity info;
print-category yes;
print-severity yes;
print-time yes;
};
category update { update_debug; };
category security { security_info; };
};
noch dazu: eth0 ist übersprungen: richtig, es bleiben aber noch eth1 & eth2. und noch was, folgenden Dateien sind leer (die ganzen zeit, nix und niemand ändert es):/var/log/syslog hat geschrieben: Nov 28 13:47:12 lansev dhcpd: Wrote 2 leases to leases file.
Nov 28 13:47:12 lansev dhcpd:
Nov 28 13:47:12 lansev dhcpd: No subnet declaration for eth0 (192.168.199.164).
Nov 28 13:47:12 lansev dhcpd: ** Ignoring requests on eth0. If this is not what
Nov 28 13:47:12 lansev dhcpd: you want, please write a subnet declaration
Nov 28 13:47:12 lansev dhcpd: in your dhcpd.conf file for the network segment
Nov 28 13:47:12 lansev dhcpd: to which interface eth0 is attached. **
Nov 28 13:47:12 lansev dhcpd:
Nov 28 13:47:20 lansev named[4812]: starting BIND 9.2.4 -u bind
Nov 28 13:47:20 lansev named[4812]: using 1 CPU
Nov 28 13:47:20 lansev named[4812]: loading configuration from '/etc/bind/named.conf'
Nov 28 13:47:20 lansev named[4812]: listening on IPv4 interface lo, 127.0.0.1#53
Nov 28 13:47:20 lansev named[4812]: listening on IPv4 interface eth0, 192.168.199.164#53
Nov 28 13:47:20 lansev named[4812]: listening on IPv4 interface eth1, 192.168.21.1#53
Nov 28 13:47:20 lansev named[4812]: listening on IPv4 interface eth2, 192.168.22.1#53
Nov 28 13:47:20 lansev named[4812]: command channel listening on 127.0.0.1#953
Nov 28 13:47:20 lansev named[4812]: command channel listening on ::1#953
Nov 28 13:47:20 lansev named[4812]: zone 0.in-addr.arpa/IN: loaded serial 1
Nov 28 13:47:20 lansev named[4812]: zone 127.in-addr.arpa/IN: loaded serial 1
Nov 28 13:47:20 lansev named[4812]: zone 168.192.in-addr.arpa/IN: could not find NS and/or SOA records
Nov 28 13:47:20 lansev named[4812]: zone 168.192.in-addr.arpa/IN: has 0 SOA records
Nov 28 13:47:20 lansev named[4812]: zone 168.192.in-addr.arpa/IN: has no NS records
Nov 28 13:47:20 lansev named[4812]: zone 255.in-addr.arpa/IN: loaded serial 1
Nov 28 13:47:20 lansev named[4812]: zone intranet/IN: could not find NS and/or SOA records
Nov 28 13:47:20 lansev named[4812]: zone intranet/IN: has 0 SOA records
Nov 28 13:47:20 lansev named[4812]: zone intranet/IN: has no NS records
Nov 28 13:47:20 lansev named[4812]: zone localhost/IN: loaded serial 1
Nov 28 13:47:20 lansev named[4812]: running
Nov 28 13:47:49 lansev dhcpd: DHCPDISCOVER from 00:0c:6e:64:19:ea via eth1
Nov 28 13:47:50 lansev dhcpd: DHCPOFFER on 192.168.21.239 to 00:0c:6e:64:19:ea via eth1
Nov 28 13:47:52 lansev dhcpd: DHCPREQUEST for 192.168.21.239 (192.168.21.1) from 00:0c:6e:64:19:ea via eth1
Nov 28 13:47:52 lansev dhcpd: DHCPACK on 192.168.21.239 to 00:0c:6e:64:19:ea via eth1
/etc/bind9/db.intranet
/etc/bind/db.168.192
/var/log/dns_update.log
/var/log/named.info
okay. dann danke ich euch sehr...
mfg bn
ich würd gerne prüfen, ob es geht, aber ich weiß nicht so ganz, wie ich das testen soll.
. ich hätte mir damit viel arbeit sparen können... 
, denn nun klappt alles wunderbar 
.