LinuxQuestions.org - DHCP and DDNS

- Linux - Networking (https://www.linuxquestions.org/questions/linux-networking-3/)

- - DHCP and DDNS (https://www.linuxquestions.org/questions/linux-networking-3/dhcp-and-ddns-335080/)

I'm running RH9 and DHCPD 3.0

I'm trying to add DNS records for all clients who receive an IP addy.

The machine that is getting it's records from the dhcp server, registers a PTR record, but not an A record. Can anyone help me figure out why my dhcp doesn't register the A record?

Here is my DHCPD.conf file

use-host-decl-names on;
option time-servers clock.redhat.com;
allow unknown-clients;
default-lease-time 120;
ddns-domainname "spew.com.";
ddns-rev-domainname "in-addr.arpa.";
ddns-update-style interim;
ddns-updates on;
allow client-updates;

max-lease-time 120;

option domain-name "spew.com.";

subnet 192.168.1.128 netmask 255.255.255.128 {
authoritative;
allow client-updates;
allow unknown-clients;
ddns-updates on;
ddns-rev-domainname "in-addr.arpa.";
ddns-domainname "spew.com.";
range 192.168.1.133 192.168.1.145;
option routers 192.168.1.129;
option broadcast-address 192.168.1.255;
option domain-name-servers 192.168.1.130, 192.168.1.132, 192.168.1.131;
option netbios-name-servers 192.168.1.132, 192.168.1.131;
option netbios-node-type 8;
option netbios-scope "";
}
zone spew.com. {
primary 192.168.1.130;
}
zone 1.168.192.in-addr.arpa. {
primary 192.168.1.130;
}

Thank you in advance

What dns server do you use?

Also the named.conf file would be helpful.

This refers to bind, so if you use something else it won't work:
If you haven't already add an allow-update { ddnsclients; }; stanza to your zone definitions (where ddnsclients is an acl which you also have to define in the config file).

Then turn on some logging.

For debugging this particular problem add something along the lines of this to your named config file:

Code:

logging {

  channel ddns {

    file "/var/log/bind/updates.log versions 5 size 1m;

    print-time yes;

    print-category yes;

  };

  category update { ddns; };

};

Have some clients do the update and check the logs for any error messages.