Opened 8 years ago

Closed 8 years ago

#1838 closed defect (wontfix)

DATASRC_QUERY_NO_ZONE logged for different situations

Reported by: jreed Owned by:
Priority: medium Milestone:
Component: Unclassified Version:
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: DNS Feature Depending on Ticket:
Estimated Difficulty: 6 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no


This is a continuation from discussion in now closed #1102.

I think there should be different log messages for logging of unknown names queried from outside and for unknown names (out-of-bailiwick) due to internal processing such as NS or CNAME RDATA lookups.

Currently both use DATASRC_QUERY_NO_ZONE.

Admins may want to understand why they received this log message and also may want to log them differently.

I was told in jabber: "I suspect that at the time it is logged, it does not know why it is looking for that data." And I was told that the new datasource should improve this.

I am opening this ticket so we can keep track of this.

Probablt the existing log entry is okay and correct at its "datasource" level. If doesn't exist, we can add two more logging messages for the DNS level.


Change History (2)

comment:1 Changed 8 years ago by jinmei

I suggest not solving this. If I understand it correctly it's only for the old implementaiton.
We should rather prioritize things for deprecating it.

comment:2 Changed 8 years ago by shane

  • Milestone New Tasks deleted
  • Resolution set to wontfix
  • Status changed from new to closed

Based on the Jabber comment and Jinmei's suggestion, I'm resolving this ticket.

Note: See TracTickets for help on using tickets.