Eu uso o isc-dhcp-server com esta configuração /etc/dhcp/dhcpd.conf
:
ddns-updates on;
ddns-update-style interim;
include "/etc/bind/rndc.key";
authoritative;
zone bat. {
primary localhost;
key rndc-key;
}
zone lan.bat. {
primary localhost;
key rndc-key;
}
zone wlan.bat. {
primary localhost;
key rndc-key;
}
zone 10.in-addr.arpa. {
primary localhost;
key rndc-key;
}
zone 50.10.in-addr.arpa. {
primary localhost;
key rndc-key;
}
zone 100.10.in-addr.arpa. {
primary localhost;
key rndc-key;
}
subnet 10.50.0.0 netmask 255.255.0.0 {
range 10.50.100.100 10.50.100.199;
interface eth0;
option domain-name-servers 10.50.0.1;
option domain-name "lan.bat";
option domain-search "lan.bat", "bat", "wlan.bat";
option routers 10.50.0.1;
option broadcast-address 10.50.255.255;
default-lease-time 600;
max-lease-time 7200;
}
subnet 10.100.0.0 netmask 255.255.0.0 {
range 10.100.100.100 10.100.100.199;
interface wlan0;
option domain-name-servers 10.100.0.1;
option domain-name "wlan.bat";
option domain-search "wlan.bat", "bat", "lan.bat";
option routers 10.100.0.1;
option broadcast-address 10.100.255.255;
default-lease-time 600;
max-lease-time 7200;
}
e bind9 com este /etc/bind/named.conf.local
:
include "/etc/bind/rndc.key";
zone "bat" {
type master;
file "/etc/bind/zones/db.bat.zone";
notify yes;
allow-update { key rndc-key; };
};
zone "lan.bat" {
type master;
file "/etc/bind/zones/db.lan.bat.zone";
notify yes;
allow-update { key rndc-key; };
};
zone "wlan.bat" {
type master;
file "/etc/bind/zones/db.wlan.bat.zone";
notify yes;
allow-update { key rndc-key; };
};
zone "10.in-addr-arpa" {
type master;
file "/etc/bind/zones/db.rev.10.in-addr-arpa.zone";
allow-update { key rndc-key; };
};
zone "50.10.in-addr-arpa" {
type master;
file "/etc/bind/zones/db.rev.50.10.in-addr-arpa.zone";
allow-update { key rndc-key; };
};
zone "100.10.in-addr-arpa" {
type master;
file "/etc/bind/zones/db.rev.100.10.in-addr-arpa.zone";
allow-update { key rndc-key; };
};
Quando me reconecto com um cliente para optar por um novo IP, o meu syslog diz:
Sep 3 07:09:12 alfred named[7393]: client 127.0.0.1#7429/key rndc-key: signer "rndc-key" approved
Sep 3 07:09:12 alfred named[7393]: client 127.0.0.1#7429/key rndc-key: updating zone 'lan.bat/IN': adding an RR at 'batmobil.lan.bat' A 10.50.100.100
Sep 3 07:09:12 alfred named[7393]: client 127.0.0.1#7429/key rndc-key: updating zone 'lan.bat/IN': adding an RR at 'batmobil.lan.bat' TXT "00b1a718622197bea9dacc93e33fb507f8"
Sep 3 07:09:12 alfred dhcpd[7367]: DHCPREQUEST for 10.50.100.100 (10.50.0.1) from 00:16:d3:39:2e:69 (batmobil) via eth0
Sep 3 07:09:12 alfred dhcpd[7367]: DHCPACK on 10.50.100.100 to 00:16:d3:39:2e:69 (batmobil) via eth0
Sep 3 07:09:12 alfred dhcpd[7367]: Added new forward map from batmobil.lan.bat to 10.50.100.100
Sep 3 07:09:12 alfred named[7393]: client 127.0.0.1#7429/key rndc-key: updating zone '10.IN-ADDR.ARPA/IN': update failed: not authoritative for update zone (NOTAUTH)
Sep 3 07:09:12 alfred dhcpd[7367]: DDNS: bad zone information, repudiating zone 50.10.in-addr.arpa.
Sep 3 07:09:12 alfred dhcpd[7367]: DDNS: Failed to retry after zone failure
Sep 3 07:09:12 alfred dhcpd[7367]: Unable to add reverse map from 100.100.50.10.in-addr.arpa. to batmobil.lan.bat: failure
Da minha pesquisa, descobri que a mensagem do nome update failed: not authoritative for update zone (NOTAUTH)
aponta para o servidor DHCP que não é autoritativo. Embora eu acredite ter identificado o problema (por favor, diga-me se estou errado), não consigo consertá-lo. Então, minha pergunta é: Como eu configuro o dhcp / bind para obter mapeamentos reversos?