Strange regression between 9.3 and 9.4

[Mark Andrews]

> 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.ar
> pa"
> > {
> > }
> >
> > @       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

	This is

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
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

	vs

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

	(one nibble less)

	Now the automatic empty zone are more specific than your zone
	so the obscure the "1 PTR localhost" record.  However if you
	create

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

	as described above it will prevent named from creating the
	corresponding empty zone automatically.

	In BIND 9.4.2 your configuration won't work.  The bug which
	allowed the record to be visible doen't exist.

$TTL 86400
@	SOA	dhcp-lab-102.englab.brq.redhat.com. atkac.redhat.com.  (
			2007061300 ; Serial
			28800      ; Refresh
			14400      ; Retry
			3600000    ; Expire
			3600 )    ; Minimum
@	NS	dhcp-lab-102.englab.brq.redhat.com.
@	PTR	localhost.

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews at isc.org