BIND 10 #1059: notify-out shouldn't look for slaves directly in the database
BIND 10 Development
do-not-reply at isc.org
Tue Jun 28 01:30:33 UTC 2011
#1059: notify-out shouldn't look for slaves directly in the database
-------------------------------------+-------------------------------------
Reporter: zzchen_pku | Owner:
Type: defect | Status: new
Priority: major | Milestone: New
Component: xfrout | Tasks
Sensitive: 0 | Keywords:
Sub-Project: DNS | Defect Severity: N/A
Estimated Difficulty: 0 | Feature Depending on Ticket:
Total Hours: 0 | Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
jelte's comments:
{{{
It is noted by TODO that it shouldn't look for slaves directly in the
database.
Certainly true, and I think we might not want the code in notify to look
for it at all (but rather have it passed
by xfrout, which also has a better chance to discover which slaves it
should not send to. I'm mainly thinking
of the problem i have right now that my bind10 is sending notifies to
itself)
}}}
--
Ticket URL: <http://bind10.isc.org/ticket/1059>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list