Opened 9 years ago

Closed 6 years ago

#965 closed defect (wontfix)

Xfrout should not notify itself

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

Description

I have a machine that gets errors sending notifies to itself:

25-May-2011 12:52:44.878 Xfrout: INFO: sending notify to 78.47.15.240#53
25-May-2011 12:52:44.879 Xfrout: INFO: sending notify to 78.47.15.240#53
25-May-2011 12:52:44.880 Xfrout: INFO: sending notify to 78.47.15.240#53
25-May-2011 12:52:44.881 Xfrout: INFO: sending notify to 78.47.15.240#53
25-May-2011 12:52:44.882 Xfrout: INFO: sending notify to 78.47.15.240#53
25-May-2011 12:52:44.882 Xfrout: INFO: notify to 78.47.15.240#53: retried exceeded

The server should be smart enough not to notify itself.

Subtickets

Change History (5)

comment:1 Changed 9 years ago by shane

  • Milestone changed from New Tasks to Year 3 Task Backlog

comment:2 Changed 8 years ago by jinmei

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

I've seen this, too, on my personal server. I propose fixing this in the next sprint.

comment:3 Changed 8 years ago by jelte

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

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.