BIND 10 #1790: update xfrin to have auth reload transfered zones
BIND 10 Development
do-not-reply at isc.org
Fri May 4 04:38:39 UTC 2012
#1790: update xfrin to have auth reload transfered zones
-------------------------------------+-------------------------------------
Reporter: | Owner: vorner
jinmei | Status: reviewing
Type: task | Milestone:
Priority: | Sprint-20120515
medium | Resolution:
Component: xfrin | Sensitive: 0
Keywords: | Sub-Project: DNS
Defect Severity: N/A | Estimated Difficulty: 3
Feature Depending on Ticket: xfr | Total Hours: 0
for in-memory |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Changes (by muks):
* owner: muks => vorner
Comment:
Hi vorner
Replying to [comment:11 vorner]:
> I also noticed one thing. Does the exception raised contain the
name/rrclass text that is being used? So the user knows what is wrong?
I had updated the name parser code sometime ago to include the string
being checked. I've updated the place where the InvalidRRClass exception
is generated now.
> Yes, that's exactly what I want to say (or, more precisely, that we
should not catch the exception at all). At least if the exception happens
in the situation described.
Updated. :)
> And, sorry for bringing it so late, but I noticed there are no tests for
the branch. Or there are and I don't see them? We definitely should have
them.
This involves orchestrating 3 different components (xfrout, xfrin and
auth) with the sqlite3+inmem configuration. The lettuce feature (#1794)
tests this:
{{{
# xfrin
When I send bind10 the command Xfrin retransfer example.org IN 127.0.0.1
47807
# xfrin logs:
Then wait for new bind10 stderr message XFRIN_TRANSFER_SUCCESS not
XFRIN_XFR_PROCESS_FAILURE
# auth logs:
Then wait for new bind10 stderr message AUTH_LOAD_ZONE
}}}
--
Ticket URL: <http://bind10.isc.org/ticket/1790#comment:12>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list