I've working on setting up and learning dynamic DNS. I'm using RH9, DHCP, and working with Bind version 9. According to my log files, the dhcpd & named services fires up with out any problems. When I go to my Win9X workstation and release/renew the IP configuration, my log file shows the following error:

Apr 30 18:19:04 trin-serv1 dhcpd: Unable to add forward map from LAPTOP.trinity-internal.com to 192.168.0.75: timed out

Can somebody point me in the right direction on what this error means? As I'm learning DNS, this could be a newbie error but a linuxquestions site and google search on this error hasn't gotten me any leads. I'd be happy to post my dhcpd.conf / named.conf config files as necessary.

Go ahead and post both of them so we can take a look. It is probably an update/key config issue.
What happens if you make a dig request specifying your local named as server? You are not blocking port 53 tcp/udp?

Tom

No. I have not blocked port 53 (I double-checked /etc/services and its open). Using dig and my server name, I get the following reply:

;; Query time: 251 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Fri Apr 30 20:40:38 2004
;; MSG SIZE rcvd: 99

this would seem to indicate to me that it using my loopback and everything is ok?

Here is my dhcpd.conf:

#
# 192.168.0.0/255.255.255.0 Scope Settings
#
subnet 192.168.0.0 netmask 255.255.255.0 {

# Range of DHCP assigned addresses for this scope
range 192.168.0.50 192.168.0.75;
# 1 day
default-lease-time 604800;
# 2 days
max-lease-time 864000;

# Configure the client's default Gateway:
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.0.255;
option routers 192.168.0.1;

# Configure the client's DNS settings:
option domain-name "trinity-internal.com";
option domain-name-servers 192.168.0.10;

# If you want the client to be configured to also use
# a WINS server:
# option netbios-name-servers 192.168.0.10;
# option netbios-node-type 8;

}

And my named.conf :

options {
directory "/var/named";
};

controls {
inet 127.0.0.1 allow { localhost; } keys { rndckey; };
};
zone "." IN {
type hint;
file "named.ca";
};

zone "localhost" IN {
type master;
file "localhost.zone";
allow-update { none; };
};

zone "0.0.127.in-addr.arpa" IN {
type master;
file "named.local";
allow-update { none; };
};

zone "trinity-internal" in {
type master;
file "trinity-internal.zone";
allow-update { localhost; };
};

zone "0.168.192.in-addr.arpa" IN {
type master;
file "192.168.0.rev";
allow-update { localhost; };
};

include "/etc/rndc.key";

None of your zones are allowing for updates from your hosts. You will have to set whatever zones you want updated to either accept based on hsts, acl, or keys.

allow-updates {"keys" "rndckey"} this will need to correspond to the host as well
or
allow-updates {192.168.0}

syntax here might not be exactly right or exactly what you need but you get the idea.

here is a link that should help

http://www.gsp.com/cgi-bin/man.cgi?s...pic=named.conf

Let us know how it works out.

Tom

I was also having the same problems - the cause was an incorrect format of files in /var/named/*.hosts & *.rev

For reverse lookup domain, something similar to the following is required:

$ORIGIN .
$TTL 38400 ; 10 hours 40 minutes
1.168.192.in-addr.arpa IN SOA hostname.domain.local. domains.domain.local. (
1076148340 ; serial - must be unique to your server
10800 ; refresh (3 hours)
3600 ; retry (1 hour)
604800 ; expire (1 week)
38400 ; minimum (10 hours 40 minutes)
)
NS hostname.domain.local.
$ORIGIN 1.168.192.in-addr.arpa.
$TTL 43200 ; 12 hours
1 PTR hostname.domain.local.


SOA, TTL, and other required parameters should also be set for yourdomain.com.hosts file in /var/named (or whereever your files are).