BIND 10 #1535: notify_out shouldn't look for NS addresses for out of zone NS names
BIND 10 Development
do-not-reply at isc.org
Wed Mar 28 15:25:43 UTC 2012
#1535: notify_out shouldn't look for NS addresses for out of zone NS names
-------------------------------------+-------------------------------------
Reporter: | Owner: UnAssigned
jinmei | Status: assigned
Type: | Milestone:
defect | Sprint-20120403
Priority: | Resolution:
medium | Sensitive: 0
Component: | Sub-Project: DNS
xfrout | Estimated Difficulty: 3
Keywords: | Total Hours: 0
Defect Severity: N/A |
Feature Depending on Ticket: |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Changes (by jelte):
* owner: jelte => UnAssigned
Comment:
ok, the change itself is simple enough, but I can't really come up with a
way to write tests for it; the datasource client is created on the fly; so
we can't really override it. And while we should consider not doing that
in the first place, it seems out of place to hack that in for the purpose
of testing this change.
I did add a few out-of-zone NS records to the database but it wouldn't
fail on that since those lookups would not result in success anyway.
So any suggestions on how else to define it (preferably without creating
an entire mock finder tree) would be nice... (if we still intend to raise
errors on find() calls of out of zone data, this would probably be very
easy to test :))
--
Ticket URL: <http://bind10.isc.org/ticket/1535#comment:6>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list