DDNS
Kevin Darcy
kcd at chrysler.com
Tue Oct 23 21:31:31 UTC 2007
The update is denied. Check your "allow-update" settings for the
relevant reverse zone(s).
- Kevin
Maguire, Jean (Gexpro, consultant) wrote:
> This is an error out of /var/log/messages file where a client is being
> denied updating the reverse lookup zone db. Any ideas? Thanks. Jean
>
>
> Oct 21 13:29:43 gesprddns05 named[4660]: client 3.100.32.52#4781: update
> '100.3.in-addr.arpa/IN' denied
>
>
> -----Original Message-----
> From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org] On
> Behalf Of Adam Tkac
> Sent: Tuesday, October 23, 2007 8:40 AM
> To: Sangoi, Nehal (Gexpro, consultant)
> Cc: Bind-Users
> Subject: Re: DDNS
>
> On Mon, Oct 22, 2007 at 05:07:08PM -0400, Sangoi, Nehal (Gexpro,
> consultant) wrote:
>
>> Hi All
>>
>> We have our bind environment running with DDNS.
>>
>> Master server and the zones are on Linux Bind 9.2.4 and windows DHCP
>> server is sending the DDNS updates to these zone files. Now, whenever
>> the lease expires for any desktop, the forward lookup zone's A record
>> of that desktop gets updated into the zone file perfectly fine but the
>>
>
>
>> DDNS is not able to delete the old reverse lookup record into the zone
>>
> file.
>
>>
>> What could be the reason for the same?
>>
>
> Are you sure that MS DHCP server sends correct DDNS updates (I mean that
> DHCP wants delete proper reverse record). If yes logging information on
> named side is your best friend. See why is update refused etc.
>
> Adam
>
> --
> Adam Tkac, Red Hat, Inc.
>
>
>
>
>
>
More information about the bind-users
mailing list