yxrrset always comes back NOTZONE

[Chris Cox]

Chris Thompson wrote:
> On Aug 17 2007, Kevin Darcy wrote:
> 
> [de-top-posted]
>                                       
>> Chris Cox wrote:
>>> I have an A record:
>>> # host ccoxprep3
>>> ccoxprep3.labs has address 10.30.81.5
>>>
>>> Using nsupdate I want to do a prereq check for the A record
>>> and add a ptr record... so...
>>>
>>> prereq yxrrset ccoxprep3.labs. IN A
>>> zone 20.10.in-addr.arpa.
>>> update delete 5.81.30.10.in-addr.arpa PTR
>>> update add  5.81.30.10.in-addr.arpa 86400 PTR ccoxprep3.labs.
>>> send
>>>
>>> But it keeps failing on the prereq yxrrset line with:
>>>
>>> update failed: NOTZONE
>>>
>>> I must be missing something obvious, anyone?
>> You're setting the zone to 20.10.in-addr.arpa, which doesn't and can't 
>> contain the 5.81.30.10.in-addr.arpa record.
> 
> And if that was just a typo, even less does it contain ccoxprep3.labs!

It was a typo, my bad... the original is correct... but still
have the same problem.

> 
> All the prereqs and updates in one DNS update transaction (i.e. "send"
> in nsupdate) must refer to RRs within a single zone.                                                          
> 

Hmmm... ok... so is it impossible then to do a yxrrset checking
for the forward record prior to trying to establish the in-addr.arpa
record?

I mean... are you saying I CAN'T do:

zone labs.
prereq yxrrset ccoxprep3.labs. IN A
send <--- with or without
zone 30.10.in-addr.arpa.
update delete 5.81.30.10.in-addr.arpa PTR
update add  5.81.30.10.in-addr.arpa 86400 PTR ccoxprep3.labs.
send

I simply want to check for the forward record before
adding the in-addr.arpa PTR record.