Strange regression between 9.3 and 9.4

[Adam Tkac]

Mark Andrews napsal(a):
>> Hi,
>>
>> I've got report that reverse IPv6 lookups in 9.4.1 series are badly 
>> broken. I have this configuration (only interesting parts are here):
>>
>> Reverse IPv6 loopback zone declaration
>> zone 
>> "0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa" 
>> IN {
>>         type master;
>>         file "named.ip6.local";
>>         allow-update { none; };
>> };
>>
>> zone file:
>> @       IN      SOA     dhcp-lab-102.englab.brq.redhat.com. 
>> atkac.redhat.com.  (
>>                                       1997022700 ; Serial
>>                                       28800      ; Refresh
>>                                       14400      ; Retry
>>                                       3600000    ; Expire
>>                                       86400 )    ; Minimum
>>        IN      NS      dhcp-lab-102.englab.brq.redhat.com.
>> 1      IN      PTR     localhost.
>>     
>
> That really should be
>
> zone "1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa"
> {
> }
>
> @       SOA     ....
> @	NS	....
> @	PTR	localhost.
>
> Only :: and ::1 (::/127) are carved out of ::/96.  You are attempting to
> carve out ::/124.
>
> Named will detect when 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa and 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa are declared as zones and not create empty zones for them.
>   
Thanks for bring light around this. If I understand correctly when admin 
declare zone for reverse IPv6 loopback like me (and all empty zones) it 
simply doesn't work. When I declared zone like you all works as 
expected. But I'm not sure what you're going to fix to 9.4.2. Will it be 
that "my" declaration will work fine?

A