bad zone transfer request of reverse addr zone
rgm at htt-consult.com
Sun Mar 3 02:14:21 UTC 2013
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 188.8.131.52 view external: bad zone transfer request:
>>>> '192-184.108.40.206.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-220.127.116.11.in-addr.arpa/IN/external: sending notifies (serial
>> Does this show that it is available in my external view?
> Try using consistent names.
> 128-18.104.22.168.in-addr.arpa != 192-22.214.171.124.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....
More information about the bind-users