BIND 10 #2427: support $ORIGIN in dns::MasterLoader
BIND 10 Development
do-not-reply at isc.org
Mon Dec 17 14:37:50 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 jreed):
Replying to [comment:11 jinmei]:
> And another interesting case:
>
> {{{
> 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
> }}}
>
> Which name should be used for the AAAA RR? RFC1035 doesn't seem to
> be clear on this point; BIND 9 uses foo.example.com; NSD uses
> bar.example.com. In my understanding, your current implementation
> behaves like NSD.
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.
We also had made this decision for the b10-loadzone. See its manual page:
"The previous origin is restored after the file is included."
See commit 31ec8c6c6598f614c77817a12d4642a5ec829c31 and test
bin/loadzone/tests/correct/include.db and the known output:
bin/loadzone/tests/correct/known.test.out
(By the way, are the existing regressions tests being used to prove the
new implementation does not regress?)
--
Ticket URL: <http://bind10.isc.org/ticket/2427#comment:12>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list