T
thommy1985
Grünschnabel
Hallo.
Ich habe ein Problem mit DDNS in Verbindung mit den oben erwähnten Programmen.
Zur erklärung:
Kleines Netzwerk: Ein fertiger Router, der die Verbindung nach außen übernimmt und das NAT bereitgestellt.
Mehrer Debian / Ubnutu und Windows Rechner + ein debian Server!
Der Debian Server übernimmt neben einigen anderen aufgaben die verteilund der IP´s per DHCP und die DNS Namensauflösung. Das macht er auch soweit ganz gut!
Probleme treten bei DDNS auf. Der Rechner stellt ein DHCPRequest, bekommt eine IP ... die Eintragung im Reservelookup findet statt... nur nicht in der "normalen" Lookup Datei.
Meine Konfig sieht wie folgt aus:
dhcpconf:
option domain-name "goebel";
option domain-name-servers serverth.goebel;
default-lease-time 600;
max-lease-time 7200;
authoritative;
log-facility local7;
allow unknown-clients;
ddns-update;
ddns-update-style interim;
update-static-leases true;
ddns-rev-domainname "162.168.192.in-addr.arpa";
ddns-domainname "goebel";
key MYKEY {
algorithm hmac-md5;
secret "bla";
};
zone 162.168.192.in-addr.arpa {
primary 192.168.162.20;
key MYKEY;
}
zone goebel{
primary 192.168.162.20;
key MYKEY;
}
subnet 192.168.162.0 netmask 255.255.255.0 {
range 192.168.162.1 192.168.162.250;
option domain-name-servers 192.168.162.20;
option routers 192.168.162.1;
host pcth {
hardware ethernet aa:bb:cc:dd:ee:ff;
fixed-address 192.168.162.2;
# option host-name "pcth";
}
host nbw {
hardware ethernet aa:bb:cc:dd:ee:ff;
fixed-address 192.168.162.5;
# option host-name "nbw";
}
host nbth {
hardware ethernet aa:bb:cc:dd:ee:ff;
fixed-address 192.168.162.3;
# option host-name "nbth";
}
}
named.conf:
include "/etc/bind/named.conf.options";
key MYKEY {
algorithm hmac-md5;
secret "abc";
};
// 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
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.0";
};
zone "255.in-addr.arpa" {
type master;
file "/etc/bind/db.255";
};
named.conf.local
zone "goebel" {
type master;
file "/etc/bind/db.goebel";
notify yes;
allow-update { key MYKEY; };
};
zone "162.168.192.in-addr.arpa" {
type master;
file "/etc/bind/db.162.168.192";
notify yes;
allow-update { key MYKEY; };
};
db.162.168.192
$ORIGIN .
$TTL 172800 ; 2 days
162.168.192.in-addr.arpa IN SOA serverth.goebel. root.serverth. (
2006032212 ; serial
28800 ; refresh (8 hours)
7200 ; retry (2 hours)
2419200 ; expire (4 weeks)
172800 ; minimum (2 days)
)
NS serverth.goebel. //manuell
$ORIGIN 162.168.192.162.168.192.in-addr.arpa.
$TTL 300 ; 5 minutes
2 PTR pcth.goebel. //automatisch -> geht
db.goebel
$TTL 3D
@ IN SOA serverth.goebel. root.serverth. (
2006032232 ; Serial
8H ; Refresh
2H ; Retry
4W ; Expire
2D ) ; TTL Negativ Cache
@ IN NS serverth.goebel.
test IN A 192.168.162.50 //manuell -> Namensauflösung geht
Aus den Logdateien beim Start geht auch nix hervor... keine Fehler
Dia Ausgabe von DHCP3:
serverth:~# dhcpd3 -d -f
Internet Systems Consortium DHCP Server V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Wrote 0 deleted host decls to leases file.
Wrote 0 new dynamic host decls to leases file.
Wrote 4 leases to leases file.
No subnet declaration for eth1 (192.168.1.20).
** Ignoring requests on eth1. If this is not what
you want, please write a subnet declaration
in your dhcpd.conf file for the network segment
to which interface eth1 is attached. **
Listening on LPF/eth0/00:a1:b0:ff:40:bc/192.168.162/24
Sending on LPF/eth0/00:a1:b0:ff:40:bc/192.168.162/24
Sending on Socket/fallback/fallback-net
Dynamic and static leases present for 192.168.162.2.
Remove host declaration pcth or remove 192.168.162.2
from the dynamic address pool for 192.168.162/24
added reverse map from 2.162.168.192.162.168.192.in-addr.arpa to pcth.goebel.
DHCPREQUEST for 192.168.162.2 from 00:15:58:65:98:84 via eth0
DHCPACK on 192.168.162.2 to 00:15:58:65:98:84 via eth0
und die von bind..
serverth:~# named -g
12-Feb-2008 21:51:51.567 starting BIND 9.3.4 -g
12-Feb-2008 21:51:51.572 found 1 CPU, using 1 worker thread
12-Feb-2008 21:51:51.676 loading configuration from '/etc/bind/named.conf'
12-Feb-2008 21:51:51.708 listening on IPv4 interface lo, 127.0.0.1#53
12-Feb-2008 21:51:51.747 listening on IPv4 interface eth0, 192.168.162.20#53
12-Feb-2008 21:51:51.828 none:0: open: /etc/bind/rndc.key: permission denied
12-Feb-2008 21:51:51.830 couldn't add command channel 127.0.0.1#953: permission denied
12-Feb-2008 21:51:51.832 none:0: open: /etc/bind/rndc.key: permission denied
12-Feb-2008 21:51:51.834 couldn't add command channel ::1#953: permission denied
12-Feb-2008 21:51:51.836 ignoring config file logging statement due to -g option
12-Feb-2008 21:51:51.857 zone 0.in-addr.arpa/IN: loaded serial 1
12-Feb-2008 21:51:51.870 zone 127.in-addr.arpa/IN: loaded serial 1
12-Feb-2008 21:51:51.885 zone 162.168.192.in-addr.arpa/IN: loaded serial 2006032212
12-Feb-2008 21:51:51.897 zone 255.in-addr.arpa/IN: loaded serial 1
12-Feb-2008 21:51:51.911 zone goebel/IN: loaded serial 2006032232
12-Feb-2008 21:51:51.924 zone localhost/IN: loaded serial 1
12-Feb-2008 21:51:51.939 running
12-Feb-2008 21:52:02.794 client 192.168.162.20#2061: updating zone '162.168.192.in-addr.arpa/IN': deleting rrset at '2.162.168.192.162.168.192.in-addr.arpa' PTR
12-Feb-2008 21:52:02.796 client 192.168.162.20#2061: updating zone '162.168.192.in-addr.arpa/IN': adding an RR at '2.162.168.192.162.168.192.in-addr.arpa' PTR
Wie gesagt: in der db.162.168.192 wird der Eintrag vorgenommen... nur nicht in der db.goebel :-(
Ich habe keine Ahnung woran das liegt und suche schon seit Tagen... Kann mir jemand helfen? Eine Idee? Ein Ansatz???
Danke... :-)
Lieben Gruß
Thomas
Ich habe ein Problem mit DDNS in Verbindung mit den oben erwähnten Programmen.
Zur erklärung:
Kleines Netzwerk: Ein fertiger Router, der die Verbindung nach außen übernimmt und das NAT bereitgestellt.
Mehrer Debian / Ubnutu und Windows Rechner + ein debian Server!
Der Debian Server übernimmt neben einigen anderen aufgaben die verteilund der IP´s per DHCP und die DNS Namensauflösung. Das macht er auch soweit ganz gut!
Probleme treten bei DDNS auf. Der Rechner stellt ein DHCPRequest, bekommt eine IP ... die Eintragung im Reservelookup findet statt... nur nicht in der "normalen" Lookup Datei.
Meine Konfig sieht wie folgt aus:
dhcpconf:
option domain-name "goebel";
option domain-name-servers serverth.goebel;
default-lease-time 600;
max-lease-time 7200;
authoritative;
log-facility local7;
allow unknown-clients;
ddns-update;
ddns-update-style interim;
update-static-leases true;
ddns-rev-domainname "162.168.192.in-addr.arpa";
ddns-domainname "goebel";
key MYKEY {
algorithm hmac-md5;
secret "bla";
};
zone 162.168.192.in-addr.arpa {
primary 192.168.162.20;
key MYKEY;
}
zone goebel{
primary 192.168.162.20;
key MYKEY;
}
subnet 192.168.162.0 netmask 255.255.255.0 {
range 192.168.162.1 192.168.162.250;
option domain-name-servers 192.168.162.20;
option routers 192.168.162.1;
host pcth {
hardware ethernet aa:bb:cc:dd:ee:ff;
fixed-address 192.168.162.2;
# option host-name "pcth";
}
host nbw {
hardware ethernet aa:bb:cc:dd:ee:ff;
fixed-address 192.168.162.5;
# option host-name "nbw";
}
host nbth {
hardware ethernet aa:bb:cc:dd:ee:ff;
fixed-address 192.168.162.3;
# option host-name "nbth";
}
}
named.conf:
include "/etc/bind/named.conf.options";
key MYKEY {
algorithm hmac-md5;
secret "abc";
};
// 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
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.0";
};
zone "255.in-addr.arpa" {
type master;
file "/etc/bind/db.255";
};
named.conf.local
zone "goebel" {
type master;
file "/etc/bind/db.goebel";
notify yes;
allow-update { key MYKEY; };
};
zone "162.168.192.in-addr.arpa" {
type master;
file "/etc/bind/db.162.168.192";
notify yes;
allow-update { key MYKEY; };
};
db.162.168.192
$ORIGIN .
$TTL 172800 ; 2 days
162.168.192.in-addr.arpa IN SOA serverth.goebel. root.serverth. (
2006032212 ; serial
28800 ; refresh (8 hours)
7200 ; retry (2 hours)
2419200 ; expire (4 weeks)
172800 ; minimum (2 days)
)
NS serverth.goebel. //manuell
$ORIGIN 162.168.192.162.168.192.in-addr.arpa.
$TTL 300 ; 5 minutes
2 PTR pcth.goebel. //automatisch -> geht
db.goebel
$TTL 3D
@ IN SOA serverth.goebel. root.serverth. (
2006032232 ; Serial
8H ; Refresh
2H ; Retry
4W ; Expire
2D ) ; TTL Negativ Cache
@ IN NS serverth.goebel.
test IN A 192.168.162.50 //manuell -> Namensauflösung geht
Aus den Logdateien beim Start geht auch nix hervor... keine Fehler
Dia Ausgabe von DHCP3:
serverth:~# dhcpd3 -d -f
Internet Systems Consortium DHCP Server V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Wrote 0 deleted host decls to leases file.
Wrote 0 new dynamic host decls to leases file.
Wrote 4 leases to leases file.
No subnet declaration for eth1 (192.168.1.20).
** Ignoring requests on eth1. If this is not what
you want, please write a subnet declaration
in your dhcpd.conf file for the network segment
to which interface eth1 is attached. **
Listening on LPF/eth0/00:a1:b0:ff:40:bc/192.168.162/24
Sending on LPF/eth0/00:a1:b0:ff:40:bc/192.168.162/24
Sending on Socket/fallback/fallback-net
Dynamic and static leases present for 192.168.162.2.
Remove host declaration pcth or remove 192.168.162.2
from the dynamic address pool for 192.168.162/24
added reverse map from 2.162.168.192.162.168.192.in-addr.arpa to pcth.goebel.
DHCPREQUEST for 192.168.162.2 from 00:15:58:65:98:84 via eth0
DHCPACK on 192.168.162.2 to 00:15:58:65:98:84 via eth0
und die von bind..
serverth:~# named -g
12-Feb-2008 21:51:51.567 starting BIND 9.3.4 -g
12-Feb-2008 21:51:51.572 found 1 CPU, using 1 worker thread
12-Feb-2008 21:51:51.676 loading configuration from '/etc/bind/named.conf'
12-Feb-2008 21:51:51.708 listening on IPv4 interface lo, 127.0.0.1#53
12-Feb-2008 21:51:51.747 listening on IPv4 interface eth0, 192.168.162.20#53
12-Feb-2008 21:51:51.828 none:0: open: /etc/bind/rndc.key: permission denied
12-Feb-2008 21:51:51.830 couldn't add command channel 127.0.0.1#953: permission denied
12-Feb-2008 21:51:51.832 none:0: open: /etc/bind/rndc.key: permission denied
12-Feb-2008 21:51:51.834 couldn't add command channel ::1#953: permission denied
12-Feb-2008 21:51:51.836 ignoring config file logging statement due to -g option
12-Feb-2008 21:51:51.857 zone 0.in-addr.arpa/IN: loaded serial 1
12-Feb-2008 21:51:51.870 zone 127.in-addr.arpa/IN: loaded serial 1
12-Feb-2008 21:51:51.885 zone 162.168.192.in-addr.arpa/IN: loaded serial 2006032212
12-Feb-2008 21:51:51.897 zone 255.in-addr.arpa/IN: loaded serial 1
12-Feb-2008 21:51:51.911 zone goebel/IN: loaded serial 2006032232
12-Feb-2008 21:51:51.924 zone localhost/IN: loaded serial 1
12-Feb-2008 21:51:51.939 running
12-Feb-2008 21:52:02.794 client 192.168.162.20#2061: updating zone '162.168.192.in-addr.arpa/IN': deleting rrset at '2.162.168.192.162.168.192.in-addr.arpa' PTR
12-Feb-2008 21:52:02.796 client 192.168.162.20#2061: updating zone '162.168.192.in-addr.arpa/IN': adding an RR at '2.162.168.192.162.168.192.in-addr.arpa' PTR
Wie gesagt: in der db.162.168.192 wird der Eintrag vorgenommen... nur nicht in der db.goebel :-(
Ich habe keine Ahnung woran das liegt und suche schon seit Tagen... Kann mir jemand helfen? Eine Idee? Ein Ansatz???
Danke... :-)
Lieben Gruß
Thomas
Zuletzt bearbeitet:
