Re: [DNSOP] Re: AS112 for TLDs

[Mark Andrews <[e-mail]>]

> This is a multi-part message in MIME format.
> --------------020009050009010201030606
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> Content-Transfer-Encoding: 7bit
> 
> Paul Vixie wrote:
> 
> >[e-mail] (Joe Baptista) writes:
> >
> >  
> >
> >>No it can't be done with BIND.  Very lame.  It would be a big asset to 
> >>root technology of the entire "*." wildcard TLD label could be pointed 
> >>to AS112.  AS112 is truly the blackhole of this universe we call the 
> >>internet.  AS112 - the internet garbage can.
> >>
> >>I support using AS112 for that.  Great way to reduce the error traffic 
> >>at root-servers.net.
> >>    
> >>
> >
> >wildcards can't be cname's or ns's.  (of the many important reasons why
> >the suggestion is terrible, that's the first/simplest that comes to mind.)
> >  
> >
> Actually no.  That is not correct.  I did some experimentation using 
> BIND 8 and 9 as root servers.  BIND 8 does not support
> 
> *. CNAME some.host.name.

	Actually all versions of BIND support "* CNAME".
 
> But BIND 9 does.
> 
> I know it sounds terrible to you but I think the RFC is flexible on 
> that.  Your the expert - you look into it.  So it would be so nice if I 
> could under BIND 9 do:
> 
> *. NS some.host.name.

	Wildcard matching has the wrong semantics (1 vs many labels)
	for NS records.  Even if the semantics where addressed you
	then have to set up nameservers to do wildcard processing
	while looking for the relevent zone.  This implies having
	a copy of the parent zone so you can know what query names
	don't match the wildcard.
 
> Paul - make it so.  It would really cut down on root traffic and we 
> could use AS112 as the garbage can of bin bucket heaven.  Be a sport - 
> push the buttons and make it so.

	Additionally the root server operators arn't worries about
	the traffic volume.  The in-addr.arpa server operators
	were worried.
 
	As a end user you should worry about information leaking
	but that can be addressed by having a local copy of the
	root zone.  There are other issues end users should also
	worry about which are also covered by having a local copy
	of the root zone.

	Mark

> regards
> joe baptista
> 
> P.S. Alot of servers already wildcard *. NS back to the IANA servers.
> 
> -- 
> Joe Baptista                                www.publicroot.org
> PublicRoot Consortium
> ----------------------------------------------------------------
> The future of the Internet is Open, Transparent, Inclusive,
> Representative & Accountable to the Internet community @large.
> ----------------------------------------------------------------
>   Office: [phone]
>      Fax: [phone]
> 
> 
> --------------020009050009010201030606
> Content-Type: text/x-vcard; charset=utf-8;
>  name="baptista.vcf"
> Content-Transfer-Encoding: 7bit
> Content-Disposition: attachment;
>  filename="baptista.vcf"
> 
> begin:vcard
> fn:Joe Baptista
> n:Baptista;Joe
> org:PublicRoot Consortium
> adr:;;963 Ford Street;Peterborough;Ontario;K9J 5V5 ;Canada
> email;internet:[e-mail]
> title:PublicRoot Representative
> tel;fax:[phone] 
> tel;cell:[phone]
> x-mozilla-html:FALSE
> url:http://www.publicroot.org
> version:2.1
> end:vcard
> 
> 
> --------------020009050009010201030606
> Content-Type: text/plain; charset="us-ascii"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline
> 
> _______________________________________________
> DNSOP mailing list
> [e-mail]
> https://www1.ietf.org/mailman/listinfo/dnsop
> 
> --------------020009050009010201030606--
> 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: [phone]                 INTERNET: [e-mail]

_______________________________________________
DNSOP mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/dnsop