How to deny update of statically assgined a/ptr records?

[Doug Barton]

On 01/16/2014 06:01 AM, Mark Andrews wrote:
>
> In message <CANV1Ld-W0A0gf33MKYHO0SSQXfXWW7tza+2NFhFhkunnAVdXrA at mail.gmail.com>
> , Oleg Gvozdev writes:
>> Hello.
>>
>> I have dynamic zone. And A record in it:
>>
>> Example(pseudo-code):
>>
>>
>> *zone myzone.*
>> *  a 10.0.0.1 domain xxx*
>>
>> Then I made DHCP update for host "host.myzone." and it receives address
>> from dynamic range (10.0.0.10-10.0.0.100), for example: 10.0.0.10.
>>
>>
>> So host.myzone. has 2 A records: 10.0.0.1 and 10.0.0.10.
>>
>> How I can configure BIND to deny updating records (for example A/PTR) for
>> hosts, that already have static A/PTR records in DNS zone ?
>
> Normally you add prerequisites to the update request to say only
> add the records if there are no records of the given type.  DHCPD
> does this by default.

... speaking of how DHCP does things, you could add a TXT record for 
your "static" entries, and test to see if that TXT record exists in DNS 
before attempting the update.

Doug