BIND 8.2.3 "update failed" messages

[Kevin Darcy]

It looks a lot like some Win2K Domain Controller is attempting those updates.
You should be able to tell where the update attempts are originating, from the
"denied update" messages in your regular logs.


- Kevin

David G. Humes wrote:

> Greetings,
>
> I just set up a new BIND 8.2.3-REL slave and have been getting the following
> messages in named.run if I turn on debugging:
>
> 12-Mar-2001 16:19:41.856 debug 1: update failed _tcp.xyz.edu 2
> 12-Mar-2001 16:19:44.090 debug 1: update failed _udp.xyz.edu 2
> 12-Mar-2001 16:19:47.554 debug 1: update failed ssd.xyz.edu 2
> 12-Mar-2001 16:19:56.972 debug 1: update failed aplsrv.xyz.edu 2
> 12-Mar-2001 16:20:10.732 debug 1: update failed _sites.xyz.edu 2
> 12-Mar-2001 16:21:56.974 debug 1: update failed _msdcs.xyz.edu 2
>
> The one thing in common with each of these zones is that they are dynamic
> zones set up to support  updates from DHCP.  But then we have some other
> dynamic zones that are not logging errors.  All the zone files seem to be up
> to date, but these messages are persistent.  Any ideas?
>
> Thanks.
>
> --Dave