BIND 10 #551: wildcard handling for memory zone: find (main cases)
BIND 10 Development
do-not-reply at isc.org
Wed Feb 16 22:33:31 UTC 2011
#551: wildcard handling for memory zone: find (main cases)
-------------------------------------+-------------------------------------
Reporter: jinmei | Owner: vorner
Type: | Status: reviewing
enhancement | Milestone: A-Team-
Priority: major | Sprint-20110223
Component: data | Resolution:
source | Sensitive: 0
Keywords: | Add Hours to Ticket: 0
Estimated Number of Hours: 8.0 | Total Hours: 0
Billable?: 1 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Comment (by jinmei):
Replying to [comment:10 jinmei]:
> > Similarly with the baz.foo.baz.bar.example.org and
*.foo.baz.bar.example.org.
> >
> > Is there a problem in the reasoning?
>
> Yes, there's a problem. By matching wild.bar.foo.example.org against
> wild.*.foo.example.org. (resulting in NXRRSET), you substitute a label
> for '*' not located in the first label of the name (in this example
> it's the second label).
Hmm, apparently I was totally confused about this case with other
corner cases. Sorry for the confusion, please forget what I've said
on this point so far. Here's a revised version of suggested tests:
- delegatedWildcard test should also check the GLUEOK case.
- emptyWildcard should check 'wild.bar.foo.example.org' results in
NXRRSET
- nestedEmptyWildcard should test:
- baz.foo.*.bar.example.org (should result in NXRRSET)
- baz.foo.baz.bar.example.org (should result in NXRRSET)
- *.foo.baz.bar.example.org (should result in NXRRSET)
- we should also test the case where we have *.example.com and
foo.example.com, with checking bar.foo.example.com doesn't match
(result in NXDOMAIN)
--
Ticket URL: <http://bind10.isc.org/ticket/551#comment:12>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list