On Tue, 2005-08-30 at 15:28 +0400, Dusan Djordjevic wrote:
> I run DNS and DHCP on Red Hat ES v3, with all updates. I want to update DNS
> tables from DHCP, so whenever client gets IP address from DHCP, it will
> automatically add it to DNS.
>
> Here is relevant part from named.conf:
>
> zone "pmsl.sd" {
> allow-update { 127.0.0.1; lan; };
> type master;
> file "pmsl.sd.zone";
> };
> zone "212.29.158.in-addr.arpa" {
> allow-update { 127.0.0.1; lan; };
> type master;
> file "212.29.158.in-addr.arpa.zone";
> };
>
> lan is ACL for local network.
>
> DHCP configuration:
> ddns-update-style interim;
>
> and in subnet part:
> option domain-name-servers 158.29.212.26;
>
> but still I have this message in logs (and of course, DNS is not updated):
>
> Aug 30 08:38:56 pmsl dhcpd: Unable to add forward map from krtws024.pmsl.sd to
> 158.29.212.100: connection refused
I do something similar on Red Hat 9.0 Linux. I had to add specific zone
details to the dhcpd.conf file (as per the manual), with a common
rndc.key file being used between the DNS and DHCP servers. Older
versions (of the servers) would allow transfers from predetermined IPs,
later versions insisted on using a keyfile.
named.conf example snippet:
--------------------------
zone "lan.example.com" {
type master;
file "lan.example.com.zone";
allow-update { key "rndckey"; };
allow-transfer { lan; };
notify yes;
};
zone "1.168.192.in-addr.arpa" {
type master;
file "1.168.192.in-addr.arpa.zone";
allow-update { key "rndckey"; };
allow-transfer { lan; };
notify yes;
};
dhcpd.conf example snippet:
--------------------------
zone lan.example.com. {
primary 192.168.1.254;
key rndckey;
}
zone 1.168.192.in-addr.arpa. {
primary 192.168.1.2;
key rndckey;
}
--
Don't send private replies to my address, the mailbox is ignored.
I read messages from the public lists.
