BIND 10 #987: b10-auth should chase CNAME in the same zone
BIND 10 Development
do-not-reply at isc.org
Fri Jun 3 06:01:54 UTC 2011
#987: b10-auth should chase CNAME in the same zone
-------------------------------------+-------------------------------------
Reporter: | Owner:
jinmei | Status: new
Type: | Milestone: Year 3 Task
defect | Backlog
Priority: major | Resolution:
Component: | Sensitive: 0
b10-auth | Sub-Project: DNS
Keywords: | Estimated Difficulty: 0.0
Defect Severity: N/A | Total Hours: 0
Feature Depending on Ticket: |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Comment (by jinmei):
Replying to [comment:3 each]:
> I haven't recently looked at BIND 10 to see how fully it supports CNAME
chains. I know that in-zone CNAME chains are provided in full by the
original sqlite3 data source code Michael and I wrote, and I gather they
are not provided by the memory data source code that has supplanted it. I
assume that our old plan of having b10-auth only serve authoritative data
and a separate b10-recurse daemon for recursion is still operative. If
those assumptions are correct, then I recommend taking no action to add
CNAME chain support to b10-auth (but do of course make sure b10-recurse
behaves correctly).
I believe the assumption still holds (and if not we'll need to tweak
many other things anyway, so not touching this part at the moment
won't be harmful).
> The subject header of this ticket specifies b10-auth, so for ''this''
ticket, I recommend no work be done at this time, and that the ticket be
closed.
Fair enough. Closing
--
Ticket URL: <http://bind10.isc.org/ticket/987#comment:4>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list