Opened 9 years ago

Closed 6 years ago

#1002 closed defect (wontfix)

various glitches in notify_out

Reported by: jinmei Owned by:
Priority: medium Milestone: Remaining BIND10 tickets
Component: xfrout Version: bind10-old
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: DNS Feature Depending on Ticket:
Estimated Difficulty: 8 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description

As I worked on #964 I found various glitches in the notify_out.py
implementation. I suspect we'll soon need fundamentally rewrite of
it (even if done incrementally) due to its current overall quality of
the code, but here are some specific points as a placeholder:

  • port number 53 is hardcoded
  • creating separate sockets for separate notify transaction seems to be a waste
  • a related note: it's not clear whether the limit of concurrent of notifies (30) is reasonable. if not, and if we allow a larger number notifies at the same time, the second point will be severer.
  • it's so heavily dependent on details of sqlite3 specific code (although not really the problem of notify_out itself)
  • it cannot send notifies to out-of-zone NSes.

Subtickets

Change History (5)

comment:1 Changed 8 years ago by jelte

  • Milestone changed from Year 3 Task Backlog to Next-Sprint-Proposed

I'd also like to see it not notify any address we are listening on ourselves

comment:2 Changed 8 years ago by jelte

  • Estimated Difficulty changed from 0.0 to 8

comment:3 Changed 8 years ago by jinmei

I guess the fact that this ticket was given an estimation of 8
suggests that we should divide the task.

comment:4 Changed 6 years ago by tomek

  • Milestone set to Remaining BIND10 tickets

comment:5 Changed 6 years ago by tomek

  • Resolution set to wontfix
  • Status changed from new to closed
  • Version set to old-bind10

This issue is related to bind10 code that is no longer part of Kea.

If you are interested in BIND10/Bundy framework or its DNS components,
please check http://bundy-dns.de.

Closing ticket.

Note: See TracTickets for help on using tickets.