cname quick question

[Mark.Andrews at nominum.com]

	Eric,
	      please cease and desist giving out this garbage "advice".

	Mark
> 
> Dear Clueless,
> 
> You don't need anyone's "permission" to put a "com" domain in your
> authoritative-only named.conf and to put a CNAME in it.  It will work just
> fine as a CNAME on a "foo.com" domain name.
> 
>         - Erik
> 
> "glen herrmannsfeldt" <gah at ugcs.caltech.edu> wrote in message
> news:983rd1$ped at gap.cco.caltech.edu...
> > Jim Reid <jim at rfc1035.com> writes:
> >
> > (snip)
> >
> > >Like Tal Dayan, you are being obtuse or deliberately provocative.
> > >Please *read* the extract from RFC1034 above. Now *think* about what
> > >it says and what that means. Pay particular attention to the last
> > >sentence. Hint: suppose clueless.example.com was a CNAME pointing at
> > >moron.example.net. That CNAME is cached by some name server. It can
> > >safely use that cached CNAME without having to query the example.com
> > >name servers to check that no other record types exist for
> > >clueless.example.com.
> >
> > It would seem that the problem is political and not technical.
> >
> > As far as I know, NSI won't put a CNAME in the root servers, thus
> > one can't have a second level CNAME.  If one wanted example.com to
> > be a CNAME for moron.com, it is technically possible (put the CNAME
> > in the .com domain).   In the pre-NSI days, this might have made
> > sense.
> >
> > -- glen
> >
> >
> >
> 
> 
> 
> 
--
Mark Andrews, Nominum Inc.
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at nominum.com