[bind10-dev] Non-absolute names for $ORIGIN

[JINMEI Tatuya / 神明達哉]

At Thu, 27 Dec 2012 19:35:11 +0100,
Peter Koch <pk at DENIC.DE> wrote:

> > > >  * Consider the name absolute, even if it doesn't end with dot.
> > > 
> > > please don't, it would violate RFC 1034, section 5.
> > > 
> > > >  * Fail if we see a name that does not end with dot.
> > > 
> > > That's not justified by RFC 1034, either.
> > 
> > I guess you mean RFC1035 for both of the above, right? (Section 5 of
> 
> absoluteley, apologies for pointing to the wrong chapter/verse, which
> shouldn't happen.
> 
> > RFC1034 is about resolvers).  Assuming so, which part of the RFC are
> > you referring to?
> > 
> > This one,
> > 
> >     $ORIGIN <domain-name> [<comment>]
> 
> Yes, that's the definition on top of page 34.
[...]
> Now, this obviously refers to what we call wire format these days.
> Section 5, bottom of page 34 is in closer context:
> 
> 	<domain-name>s make up a large share of the data in the master file.
> 	The labels in the domain name are expressed as character strings and
> 	separated by dots.  Quoting conventions allow arbitrary characters to be
> 	stored in domain names.  Domain names that end in a dot are called
> 	absolute, and are taken as complete.  Domain names which do not end in a
> 	dot are called relative; the actual domain name is the concatenation of
> 	the relative part with an origin specified in a $ORIGIN, $INCLUDE, or as
> 	an argument to the master file loading routine.  A relative name is an
> 	error when no origin is available.

Okay, then it matched what I guessed.  I'm not so sure if it clearly
allows the use of non absolute form in $ORIGIN, though (rather, I
suspect it was not the intent of the original author of the RFC, but
that's a guess).  But in any case, we didn't choose either of the
above two:
* Consider the name absolute, even if it doesn't end with dot.
* Fail if we see a name that does not end with dot.

and implemented this one for BIND 10:
* Warn if we see a name that does not end with dot (for $ORIGIN)

---
JINMEI, Tatuya
Internet Systems Consortium, Inc.