Dynamic DNS - DHCP Error

[HKDude]

I'm working on learning DNS so I'm sadly at 'newbie' status on that topic. I've been working off Void Main's dynamic DNS instructions and have that implemented. All is well. I have the appropriate files modified and in place, the services (named & dhcpd) are running and appear happy. When I go to and release/renew a windows win9x client, I see the following error in the logs:

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

If somebody could give me a push in the right direction and tell me what to look for, I would appreciate it. As I'm not sure if its DNS or DHCP, I haven't posted any config files (who wants to scroll through 10 pages of unecessary config files?) but I can/will as needed. I'm hoping this is a newbie error...

[creeping]

I'm getting exactly the same error message and I'm using the example DNS/DHCP voidmain config files. Dhcpd and named are not showing any other error messages.

Does anyone have an insight as to why this could be occurring. The client machines that are obtaining the DHCP leases are WinXP if that helps. Also I'm using FC2.

Thanks

[Void Main]

Hmmm, I guess I missed the first message in this thread. Just curious if you also have the same problem with Linux clients? I don't have any Windows machines left so I can't really try and duplicate it. I will dig around on the bind sites to see if I can find out why this might be happening.

[creeping]

Sorry I went back and checked the logs and named and dhcp was reporting this:

Jul 16 08:38:35 death named[12227]: shutting down: flushing changes
Jul 16 08:38:35 death named[12227]: stopping command channel on 127.0.0.1#953
Jul 16 08:38:35 death named[12227]: no longer listening on 127.0.0.1#53
Jul 16 08:38:35 death named[12227]: no longer listening on 192.168.0.2#53
Jul 16 08:38:35 death named: succeeded
Jul 16 08:38:35 death named[12227]: exiting
Jul 16 08:38:37 death named[17988]: starting BIND 9.2.3 -u named
Jul 16 08:38:37 death named: named startup succeeded
Jul 16 08:38:37 death named[17988]: using 1 CPU
Jul 16 08:38:37 death named[17988]: loading configuration from '/etc/named.conf'
Jul 16 08:38:37 death named[17988]: listening on IPv4 interface lo, 127.0.0.1#53
Jul 16 08:38:37 death named[17988]: listening on IPv4 interface eth0, 192.168.0.2#53
Jul 16 08:38:38 death named[17988]: command channel listening on 127.0.0.1#953
Jul 16 08:38:38 death named[17988]: zone 0.0.127.in-addr.arpa/IN: loaded serial 1
Jul 16 08:38:38 death named[17988]: zone 0.168.192.in-addr.arpa/IN: loaded serial 1
Jul 16 08:38:38 death named[17988]: zone voidmain.home/IN: loaded serial 1
Jul 16 08:38:38 death named[17988]: zone localhost/IN: loaded serial 1
Jul 16 08:38:38 death named[17988]: running
Jul 16 08:39:32 death dhcpd: Internet Software Consortium DHCP Server V3.0.1rc12
Jul 16 08:39:32 death dhcpd: Copyright 1995-2003 Internet Software Consortium.
Jul 16 08:39:32 death dhcpd: All rights reserved.
Jul 16 08:39:32 death dhcpd: For info, please visit http://www.isc.org/products/DHCP
Jul 16 08:39:32 death dhcpd: Wrote 2 leases to leases file.
Jul 16 08:39:32 death dhcpd: Listening on LPF/eth0/00:10:4b:0d:0e:e9/192.168.0.0/24
Jul 16 08:39:32 death dhcpd: Sending on LPF/eth0/00:10:4b:0d:0e:e9/192.168.0.0/24
Jul 16 08:39:32 death dhcpd: Sending on Socket/fallback/fallback-net
Jul 16 08:40:11 death named[17988]: client 192.168.0.2#33243: updating zone 'voidmain.home/IN': adding an RR
Jul 16 08:40:11 death named[17988]: client 192.168.0.2#33243: updating zone 'voidmain.home/IN': adding an RR
Jul 16 08:40:11 death named[17988]: journal file voidmain.home.zone.jnl does not exist, creating it
Jul 16 08:40:11 death named[17988]: voidmain.home.zone.jnl: create: permission denied
Jul 16 08:40:11 death named[17988]: client 192.168.0.2#33243: updating zone 'voidmain.home/IN': error: journal open failed: unexpected error
Jul 16 08:40:11 death dhcpd: Unable to add forward map from creeping.voidmain.home to 192.168.0.198: timed out
Jul 16 08:40:11 death dhcpd: DHCPREQUEST for 192.168.0.198 from 00:05:1c:0a:1d:4f (creeping) via eth0
Jul 16 08:40:11 death dhcpd: DHCPACK on 192.168.0.198 to 00:05:1c:0a:1d:4f (creeping) via eth0

Does it mean that I have some file permission or named update configurations incorrect set?

[Void Main]

Yes, try:

# chown -R named:named /var/named

then

# /sbin/service named restart

what's the log look like after doing this?