het wil maar niet lukken.
ik draai debian 3.1 en ik probeer dus mijn dns te update i.c.m dhcp3.
maar elke keer lijkt er iets mis te gaan met de key's.
ik heb uitraart geprobeerd de oplossing op google te vinden maar niets lijkt te helpen.
ik heb de volgende tut gebruikt : http://www.debian-administration.org/articles/343
en krijg de volgende fout melding in mijn syslog:
ik heb het ondertussen ook op een andere manier geprobeerd die ik op internet had gevonden vandaar dat mijn config files er iets anders uit zien dan in de tut.
named.conf
dhcpd.conf
Alvast bedankt voor julie hulp
ik draai debian 3.1 en ik probeer dus mijn dns te update i.c.m dhcp3.
maar elke keer lijkt er iets mis te gaan met de key's.
ik heb uitraart geprobeerd de oplossing op google te vinden maar niets lijkt te helpen.
ik heb de volgende tut gebruikt : http://www.debian-administration.org/articles/343
en krijg de volgende fout melding in mijn syslog:
code:
1
2
3
4
| Feb 27 14:42:16 superman-server named[7935]: client 127.0.0.1#33003: request has invalid signature: tsig verify failure Feb 27 14:42:16 superman-server dhcpd: Unable to add forward map from superman.network.athome. to 192.168.0.10: bad DNS key Feb 27 14:42:16 superman-server dhcpd: DHCPREQUEST for 192.168.0.10 from 00:13:d4:9e:3e:a4 (superman) via eth0 Feb 27 14:42:16 superman-server dhcpd: DHCPACK on 192.168.0.10 to 00:13:d4:9e:3e:a4 (superman) via eth0 |
ik heb het ondertussen ook op een andere manier geprobeerd die ik op internet had gevonden vandaar dat mijn config files er iets anders uit zien dan in de tut.
named.conf
code:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
| // 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
#controls {
# inet 127.0.0.1 allow {localhost; } keys { "rndc-key"; };
#};
key "rndc-key" {
algorithm hmac-md5;
secret "uOKrFtzHm/QaeVArg4liOw==";
};
controls {
inet 127.0.0.1 port 953
allow { 127.0.0.1; } keys { "rndc-key"; };
};
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
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";
};
// 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 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"; |
dhcpd.conf
code:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
| # Basic stuff to name the server and switch on updating
server-identifier 192.168.0.3;
ddns-updates on;
ddns-update-style interim;
ddns-domainname "network.athome.";
ddns-rev-domainname "in-addr.arpa.";
ignore client-updates;
# This is the key so that DHCP can authenticate it's self to BIND9
#include "/etc/bind/rndc.key";
key "rndc-key" {
algorithm hmac-md5;
secret "uOKrFtzHm/QaeVArg4liOw==";
};
# This is the communication zone
zone network.athome. {
primary 127.0.0.1;
key rndc-key;
}
# Normal DHCP stuff
option domain-name "network.athome.";
option domain-name-servers 192.168.0.3, 192.168.0.1;
option ntp-servers 192.168.0.3;
option ip-forwarding off;
default-lease-time 600;
max-lease-time 7200;
authoritative;
log-facility local7;
subnet 192.168.0.0 netmask 255.255.255.0 {
range 192.168.0.5 192.168.0.200;
option broadcast-address 192.168.0.255;
option routers 192.168.0.2;
allow unknown-clients;
zone 0.168.192.in-addr.arpa. {
primary 192.168.0.3;
key "rndc-key";
}
zone localdomain. {
primary 192.168.0.3;
key "rndc-key";
}
} |
Alvast bedankt voor julie hulp
Yesterday is history. Tomorrow is a mystery. Today is a gift, that’s why we call it the present.