Re: Local DNS... "unknown host"

>Yes, you should have entries in the zone file for the domain listing
>hostnames to IP's and in the 1.168.192.in-addr.arpa zone file listing
>192.168.1.x IP's to hostnames. This works best if LAN IP's are static.
>It gets more complicated if trying to do it automatically with dhcp.

Okay, well unfortunately I am using DHCP. I've been doing a bit of
reading on DDNS. However, now after configuring DDNS my clients cannot
receive an ip address:

DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPOFFER from 127.0.0.1
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPREQUEST on eth0 to 255.255.255.255 port 67
[5 more DHCPDISCOVER attempts]
NO DHCPOFFERS received.
No working leases in persistent database. Sleeping.

Here is what my dhcp configuration looks like (dhcp.conf):

server-identifier alisa.weichert-local;
authoritative;
ddns-update-style interim;
ddns-updates on;

subnet 192.168.1.0 netmask 255.255.255.0 {
authoritative;
allow client-updates;
ddns-updates on;
ddns-rev-domainname "weichert-local";
option routers 192.168.1.1;
option subnet-mask 255.255.255.0;
option domain-name-servers 192.168.1.1;
option ip-forwarding on;
option domain-name weichert-local;
range dynamic-bootp 192.168.1.2 192.168.1.254;
default-lease-time 21600;
max-lease-time 43200;
one-lease-per-client on;
}
host DI-614 {
hardware ethernet 00:40:05:b8:00:36;
fixed-address 192.168.1.254;
}

Any ideas? Thanks again.
Mike

.