BIND 10 #2427: support $ORIGIN in dns::MasterLoader
BIND 10 Development
do-not-reply at isc.org
Mon Dec 17 14:53:08 UTC 2012
#2427: support $ORIGIN in dns::MasterLoader
-------------------------------------+-------------------------------------
Reporter: jinmei | Owner:
Type: task | vorner
Priority: medium | Status:
Component: libdns++ | reviewing
Keywords: | Milestone:
Sensitive: 0 | Sprint-20121218
Sub-Project: DNS | Resolution:
Estimated Difficulty: 3 | CVSS Scoring:
Total Hours: 0 | Defect Severity: N/A
| Feature Depending on Ticket:
| loadzone-ng
| Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
Comment (by vorner):
Hello
Replying to [comment:12 jreed]:
> > {{{
> > foo.example.com. IN A 192.0.2.1
> > $INCLUDE some_file ; which ends with "bar.example.com. IN A 192.0.2.2"
> > IN AAAA 2001:db8::1
> > }}}
>
> RFC 1035 seems clear to me: "Note that a $INCLUDE entry never changes
the relative
> origin of the parent file, regardless of changes to the relative origin
> made within the included file." I think that is a bug in nsd.
Actually, if you look, the case here is not about origin at all, but about
the last seen name. So this part of RFC clearly does not apply.
But I'm adopting the bind9 approach.
> (By the way, are the existing regressions tests being used to prove the
new implementation does not regress?)
I guess they'll be once the old loader is replaced. But until the loader
is actually used in something user-visible from outside, then hardly.
--
Ticket URL: <http://bind10.isc.org/ticket/2427#comment:13>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list