DDNS dhcp3 und bind9 "timed out" :(

[Sallos]

Tach ich hab ein Problem mit meinen Lan Server auf dem ich Bind9 + Dhcp3 instaliert habe.

Ich habe die Configs nach dem Muster von http://www.schoki.org/ddns erstellt.

Erstes Problem:
Wenn ich versuche den Bind9 zu stopen bekomme ich folgende Fehlermeldung!!
Ich muss immer neustarten nach jeder Änderung

Code: Alles auswählen

gsg:~# /etc/init.d/bind9 stop
Stopping domain name service...: bindrndc: connection to remote host closed
This may indicate that the remote server is using an older version of
the command protocol, this host is not authorized to connect,
or the key is invalid.
 failed!
gsg:~# /etc/init.d/bind9 start
Starting domain name service...: bind failed!
gsg:~#

Zweites Problem:

Wenn ich einen Rechener einstecke bekomme ich im Syslog folgende Fehlermeldung:

Code: Alles auswählen

Jun  3 21:47:43 localhost dhcpd: Unable to add forward map from NotebookLS.gsg.lan to 192.168.3.200: timed out
Jun  3 21:47:43 localhost dhcpd: DHCPREQUEST for 192.168.3.200 from 00:0a:e4:a0:51:ef (NotebookLS) via eth1
Jun  3 21:47:43 localhost dhcpd: DHCPACK on 192.168.3.200 to 00:0a:e4:a0:51:ef (NotebookLS) via eth1

dhcp.conf

Code: Alles auswählen

server-identifier gsg.gsg.lan;
authoritative;
ddns-update-style interim;

key mykey {
algorithm hmac-md5;
secret 86U1XYQ0PPS2IHQmY6EFdA==;
};

zone gsg.lan. {
primary 192.168.3.10;
key mykey;
}

zone 3.168.192.in-addr.arpa. {
primary 192.168.3.10;
key mykey;
}

subnet 192.168.3.0 netmask 255.255.255.0 {

option subnet-mask 255.255.255.0;
range 192.168.3.100 192.168.3.200;
option broadcast-address 192.168.3.255;
option domain-name "gsg.lan";
one-lease-per-client on;
default-lease-time 14400;
max-lease-time 14401;
option ip-forwarding off;
option time-offset -18000;
option domain-name-servers 192.168.3.10;
}

named.conf

Code: Alles auswählen

// 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";
///////////////////////////Lars
key mykey {
algorithm hmac-md5;
secret 86U1XYQ0PPS2IHQmY6EFdA==;
};
///////////////////////////////



// 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.255";
};

//////////////////////////////Lars
zone "gsg.lan" {
type master;
file "/var/cache/bind/gsg.zone";
allow-update { key mykey; };
};

zone "3.168.192.in-addr.arpa" {
type master;
file "/var/cache/bind/3.168.192.zone";
allow-update { key mykey; };
};
///////////////////////////////////////





// zone "com" { type delegation-only; };
// zone "net" { type delegation-only; };

// From the release notes:
//  Because many of our users are uncomfortable receiving undelegated answers
//  from root or top level domains, other than a few for whom that behaviour
//  has been trusted and expected for quite some length of time, we have now
//  introduced the "root-delegations-only" feature which applies delegation-only
//  logic to all top level domains, and to the root domain.  An exception list
//  should be specified, including "MUSEUM" and "DE", and any other top level
//  domains from whom undelegated responses are expected and trusted.
// root-delegation-only exclude { "DE"; "MUSEUM"; };

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

Ich hoffe mir kann da jemand helfen....



MfG


Lars

[herrchen]

Code: Alles auswählen

this host is not authorized to connect,

hast du auch die änderungen in der "/etc/bind/named.conf.options" bezüglich "controls" vorgenommen?

herrchen

[Sallos]

Ja hab ich.

So sieht sie aus:

Code: Alles auswählen

/////////////////////////////Lars
acl "lan" {192.168.3.0/24; 127.0.0.1;};

controls {
inet 127.0.0.1 port 953 allow { 127.0.0.1; 192.168.3.10; } keys { "mykey";};
};
////////////////////////////////////////



options {
	directory "/var/cache/bind";

	// If there is a firewall between you and nameservers you want
	// to talk to, you might need to uncomment the query-source
	// directive below.  Previous versions of BIND always asked
	// questions using port 53, but BIND 8.1 and later use an unprivileged
	// port by default.

	// query-source address * port 53;

	// If your ISP provided one or more IP addresses for stable 
	// nameservers, you probably want to use them as forwarders.  
	// Uncomment the following block, and insert the addresses replacing 
	// the all-0's placeholder.

	// forwarders {
	// 	0.0.0.0;
	// };

/////////////////Lars
allow-query { "lan"; };
//////////////////////

	auth-nxdomain no;    # conform to RFC1035
	listen-on-v6 { any; };
};

[Sallos]

Hat keiner einen Verdacht waran das liegen kann?