bad zone transfer request of reverse addr zone

[Robert Moskowitz]

On 03/01/2013 06:42 PM, Mark Andrews wrote:
> In message <5130FBA0.3020500 at htt-consult.com>, Robert Moskowitz writes:
>> On 03/01/2013 01:50 PM, Jan-Piet Mens wrote:
>>>> I get this for all my secondaries for my reverse domain:
>>>>
>>>> client 63.68.132.50 view external: bad zone transfer request:
>>>> '192-26.67.83.208.in-addr.arpa/IN': non-authoritative zone
>>>> (NOTAUTH): 23 Time(s)
>>> The zone is either not defined in the view the client is accessing,
>>> and/or it wasn't loaded due to errors, which effectively is the same.
>>>
>>> Check startup logs to see if zone contains errors, and make sure the
>>> zone is available in your 'external' view.
>> Mar  1 12:42:01 onlo named[1405]: zone
>> 128-26.67.83.208.in-addr.arpa/IN/external: sending notifies (serial
>> 2013022501)
>>
>> Does this show that it is available in my external view?
> Try using consistent names.
>
> 	128-26.67.83.208.in-addr.arpa != 192-26.67.83.208.in-addr.arpa

ARGH!!!!

Can't see the trees from the forest.  I 'blame' my dyselxia; yeah no 
excuse.  Now to dig in to see what is wrong here....