DNS, DHCPD setup: Strange named error in messages: prerequisite not satisfied NXRRSET

I have configured my LAN to used DNS and DHCPD. The servers are
running on a Fedora 7 PC and the clients are a mixture of desktops and
laptops running Windows XP Home SP2. On the surface all seems to work
as it should. However, I have one problem and I hope I can explain it
in this scenario.

One of the laptops is used statically 85% of the time in my office.
The other 15% of the time I like to use this laptop in other parts of
the house (living room, bedroom, etc). When I do, I switch to the
wireless adaptor. Thereby, the DHCPD server offers a different IP
address. The host name stays the same though. The address is accepted
and the server acknowledges. However, the new DNS "A" record fails to
be written to the forward and reverse zone files. I really don't know
what questions to ask but maybe the probem is that a host name already
exist and is mapped to an IP address in the zone files. Does the IP
have to expire first and remove the host name/IP mapp from the zone
files before an update can take place? Or is this a bug?


These errors are captured in /var/log/messages:

Jan 16 01:55:00 linux dhcpd: DHCPDISCOVER from 00:1c:26:49:b1:c8
(VOSTRO) via eth0
Jan 16 01:55:01 linux dhcpd: DHCPOFFER on 192.168.0.128 to 00:1c:
26:49:b1:c8 (VOSTRO) via eth0
Jan 16 01:55:01 linux dhcpd: DHCPREQUEST for 192.168.0.128
(192.168.0.202) from 00:1c:26:49:b1:c8 (VOSTRO) via eth0
Jan 16 01:55:01 linux dhcpd: DHCPACK on 192.168.0.128 to 00:1c:
26:49:b1:c8 (VOSTRO) via eth0
Jan 16 01:55:21 linux dhcpd: DHCPDISCOVER from 00:1c:23:8d:96:47
(VOSTRO) via eth0
Jan 16 01:55:22 linux dhcpd: DHCPOFFER on 192.168.0.127 to 00:1c:23:8d:
96:47 (VOSTRO) via eth0
Jan 16 01:55:22 linux named[16894]: client 192.168.0.202#32844:
updating zone 'linux.org/IN': update unsuccessful: VOSTRO.linux.org
ame not in use' prerequisite not satisfied (YXDOMAIN)
Jan 16 01:55:22 linux named[16894]: client 192.168.0.202#32844:
updating zone 'linux.org/IN': update unsuccessful: VOSTRO.linux.org
: 'RRset exists (value dependent)' prerequisite not satisfied
(NXRRSET)
Jan 16 01:55:22 linux dhcpd: Forward map from VOSTRO.linux.org. to
192.168.0.127 FAILED: Has an A record but no DHCID, not mine.


This is the content of my dhcpd.conf:

# DHCP Server Configuration file.
#

authoritative;

server-identifier linux;
ddns-domainname "linux.org.";
ddns-rev-domainname "in-addr.arpa.";
ddns-update-style interim;
ddns-updates on;
do-forward-updates on;
allow client-updates;

key mykey {
algorithm hmac-md5;
secret "secret-key-hash";
};


zone linux.org. {
primary linux;
key mykey;
}

zone 0.168.192.in-addr.arpa. {
primary linux;
key mykey;
}

subnet 192.168.0.0 netmask 255.255.255.0 {

# The range of IP addresses the server
# will issue to DHCP enabled PC clients
# booting up on the network

range 192.168.0.121 192.168.0.129;

# Set the amount of time in seconds that
# a client may keep the IP address

# default-lease-time 86400;
# max-lease-time 86400;

default-lease-time 259200;
max-lease-time 259200;

# Set the default gateway to be used by
# the PC clients

option routers 192.168.0.1;

# Don't forward DHCP requests from this
# NIC interface to any other NIC
# interfaces

option ip-forwarding off;

# Set the broadcast address and subnet mask
# to be used by the DHCP clients

option broadcast-address 192.168.0.255;
option subnet-mask 255.255.255.0;

# Set the DNS server to be used by the
# DHCP clients

option domain-name "linux.org";
option domain-name-servers 192.168.0.202;

# Set the NTP server to be used by the
# DHCP clients

#option nntp-server 192.168.1.202;

# If you specify a WINS server for your Windows clients,
# you need to include the following option in the dhcpd.conf file:

option netbios-name-servers 192.168.0.202;

}


This is the content of my named.conf:

// named.conf
//

key mykey {
algorithm hmac-md5;
secret "secret-key-hash";
};

acl "home" { 192.168.0.0/24; 127.0.0.1; };

options {
allow-query { "home"; };
};

controls {
inet 127.0.0.1 port 953
allow { 127.0.0.1; } keys { "mykey"; };
};

zone "linux.org" IN {
type master;
file "/var/named/linux.zone";
allow-update { key mykey; };
allow-query { any; };
notify no;
};

zone "0.168.192.in-addr.arpa" IN {
type master;
file "/var/named/192-168-0.zone";
allow-update { key mykey; };
allow-query { any; };
notify no;
};
.

Relevant Pages

  • Re: Moving DNS to New Server
    ... single ADI zone. ... I've set up a new server as a DC. ... Another thread pointed out that an ADI zone will replicate to any DNS ... It may be a simpler solution to update the DHCP scope and have the clients ...
    (microsoft.public.win2000.dns)
  • Re: DDNS entries disapearing
    ... >> registration is trying to go into the child server, ... > The clients receive the same config through scope options 006 DNS ... hosting the Primary zone, and the otherare hosting a secondary of this ...
    (microsoft.public.win2000.dns)
  • Re: Web site viewable from outside office but not on Lan
    ... If I delete the zone rgsassociates.com and recreate it will that affect our ... This server is also our Exchange server and email comes in at ... > on one of the clients and then try accessing www.ourcompany.com from that ... We also host a 3rd site for one of our ...
    (microsoft.public.windows.server.dns)
  • Re: How to disable DNS update for 1 record
    ... Clients at 1st location use DNS1 as primary server and DNS2 as ... then they replicate the entire zone. ...
    (microsoft.public.windows.server.dns)
  • dhcp wont updated dns tables, RHEL, ES
    ... so I can't ping client_name even though dhcpd has given client_name the ... The clients are mostly PC's. ... But I have a service on the nice server that requires it to ... Mar 5 10:36:05 aon3 dhcpd: All rights reserved. ...
    (linux.redhat)
Loading