bad zone transfer request of reverse addr zone
rgm at htt-consult.com
Sun Mar 3 03:22:55 UTC 2013
On 03/02/2013 09:14 PM, Robert Moskowitz wrote:
> 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 18.104.22.168 view external: bad zone transfer request:
>>>>> '192-22.214.171.124.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: zone
>>> 128-126.96.36.199.in-addr.arpa/IN/external: sending notifies (serial
>>> Does this show that it is available in my external view?
>> Try using consistent names.
>> 128-188.8.131.52.in-addr.arpa != 192-184.108.40.206.in-addr.arpa
> 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....
The 'problem' is with one of my secondaries that is not configured for
the right zone. I will contact the admin to fix that. There is a bit
of history behind the name of this zone that does not matter; only
recognizing the problem and fixing it.
thanks for helping me see the trees clearly.
More information about the bind-users