prerequisite not satisfied???
Kevin Darcy
kcd at daimlerchrysler.com
Fri Sep 15 00:11:15 UTC 2006
Tony Ewell wrote:
> Hi All,
>
> I am using Cent OS 4.3 (same as Red Hat Enterprise
> Linux, only cheaper). And:
>
> rpm -qa \*bind\*
> bind-chroot-9.2.4-2
>
> In my /var/named/chroot/var/named/slaves/named-update-debug.log,
> I am getting the following error message:
>
> Sep 14 08:00:23.641 update: info: client 127.0.0.1#32770: updating zone
> 'xxxxxx.local/IN': update failed: 'name
>
> not in use' prerequisite not satisfied (YXDOMAIN)
> Sep 14 08:00:23.653 update: info: client 127.0.0.1#32770: updating zone
> 'xxxxxx.local/IN': deleting an rrset
>
> Sep 14 08:00:23.653 update: info: client 127.0.0.1#32770: updating zone
> 'xxxxxx.local/IN': adding an RR
>
> Sep 14 08:00:23.653 update: info: client 127.0.0.1#32770: updating zone
> '255.168.192.in-addr.arpa/IN': deleting
> an rrset
>
> Sep 14 08:00:23.654 update: info: client 127.0.0.1#32770: updating zone
> '255.168.192.in-addr.arpa/IN': adding an
> RR
>
>
> What does it mean and how do I correct it?
>
A prerequisite (or more than 1 prerequisite) can be set on a Dynamic
Update transaction by the client or client app, and if the prerequisite
isn't met, then the update is not performed.
Whatever app is generating these particular Dynamic Updates is failing
some of them due to the fact they prerequisite(s) they set weren't met.
This is probably harmless, but if you want to double-check, then consult
the logs and/or documentation of the relevant app (probably a DHCP
server) to see what prereqs it is setting, and what it does in the case
of a prereq-based failure.
- Kevin
More information about the bind-users
mailing list