> On Wed, Sep 06, 2006 at 12:39:27PM -0400, Joe Abley wrote:
> > 
> > On 6-Sep-2006, at 12:03, [EMAIL PROTECTED] wrote:
> > 
> > >        so as a lone disenting voice in the wilderness, i think  
> > >this is
> > >   a bad idea ... and i am a bit resentful that ISC implemented
> > >   such features before the IETF sactioned them.  (yet another code
> > >   patch that I must make -every- time i update BIND code from ISC)
> > 
> > Just to be clear, what have ISC implemented, and in what versions of  
> > BIND? Is there new behaviour which is on by default which causes  
> > resolvers to answer the queries discussed in this draft locally?
> 
> 
>       ISC has implemented this in at least 9.3.2 and 9.3.2-P1:

        ISC has NOT implemented this in 9.3.2 or 9.3.2-P1.
        
        It is in BIND 9.4.0 which is currently at rc2.  It can also
        be disabled at runtime with a single named.conf option.
 
> Sep  6 04:01:09 shim named[13388]: automatic empty zone: D.F.IP6.ARPA
> Sep  6 04:01:09 shim named[13388]: automatic empty zone: 8.E.F.IP6.ARPA
> Sep  6 04:01:09 shim named[13388]: automatic empty zone: 9.E.F.IP6.ARPA
> Sep  6 04:01:09 shim named[13388]: automatic empty zone: A.E.F.IP6.ARPA
> Sep  6 04:01:09 shim named[13388]: automatic empty zone: B.E.F.IP6.ARPA
> Sep  6 05:01:16 shim named[13388]: automatic empty zone: 127.IN-ADDR.ARPA
> Sep  6 05:01:16 shim named[13388]: automatic empty zone: 254.169.IN-ADDR.ARPA
> Sep  6 05:01:16 shim named[13388]: automatic empty zone: 2.0.192.IN-ADDR.ARPA
> Sep  6 05:01:16 shim named[13388]: automatic empty zone: 255.255.255.255.IN-A
> DDR.ARPA
> Sep  6 05:01:16 shim named[13388]: automatic empty 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.0.IP6.ARPA
> Sep  6 05:01:16 shim named[13388]: automatic empty 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
> 
> ...
> 
>       which seems just a bit preumptious ... 
>       the existence of these "empty" zones does have interesting
>       behaviour for resolvers that use a server where such zones
>       are created.
> 
>       are these prefixes properly accounted for, with delegation
>       authority by either the IANA or any of the RIRS to your knowledge?
>       Does the IETF even have the authority to make address/prefix delegation
> s?
> 
>       the answer is no, to all questions, to my understanding.
>       and so I have to rip out this code from the ISC distribution.
> 
> --bill
> > 
> > Joe
> > 
> .
> dnsop resources:_____________________________________________________
> web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
> mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html
--
ISC Training!  October 16-20, 2006, in the San Francisco Bay Area,
covering topics from DNS to DHCP.  Email [EMAIL PROTECTED]
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: [EMAIL PROTECTED]
.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html

Reply via email to