Opened 8 years ago

Closed 6 years ago

#2031 closed defect (wontfix)

NSAS permanently cache unreachable namservers?

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

Description

A query continually resulted with SERVFAIL even 6 days after the first problem.
The initial logs showed:

2012-06-01 00:12:44.449 DEBUG [b10-resolver.reslib] RESLIB_NXDOM_NXRR NXDOMAIN/NXRRSET received in response to query for <ns.norplex-communications.net. IN AAAA>
2012-06-01 00:12:44.449 DEBUG [b10-resolver.nsas] NSAS_EMPTY_RESPONSE response to query for ns.norplex-communications.net. returned an empty answer section
...
2012-06-01 00:12:44.458 DEBUG [b10-resolver.reslib] RESLIB_NXDOM_NXRR NXDOMAIN/NXRRSET received in response to query for <ns.norplex-communications.com. IN AAAA>
2012-06-01 00:12:44.458 DEBUG [b10-resolver.nsas] NSAS_EMPTY_RESPONSE response to query for ns.norplex-communications.com. returned an empty answer section
...
2012-06-01 00:12:48.286 DEBUG [b10-resolver.nsas] NSAS_ERROR_RESPONSE error response of SERVFAIL returned in query for ns.norplex-communications.com.
2012-06-01 00:12:48.286 DEBUG [b10-resolver.nsas] NSAS_ERROR_RESPONSE error response of SERVFAIL returned in query for ns.norplex-communications.net.
2012-06-01 00:12:48.286 DEBUG [b10-resolver.reslib] RESLIB_RUNQ_FAIL failure callback - nameservers are unreachable
2012-06-01 00:12:48.286 DEBUG [b10-resolver.reslib] RESLIB_RUNQ_FAIL failure callback  nameservers are unreachable

So then later queries would not even attempt to use the nameservers recorded with problems:

2012-06-06 00:10:56.084 DEBUG [b10-resolver.reslib] RESLIB_RUNQ_FAIL failure callback - nameservers are unreachable

This ticket is not about wrongly recording that they are unreachable when they were but about recording this info for long time. (When I restarted b10-resolver it worked correctly for my lookup.)

The goal of this ticket is so the NSAS doesn't permanently cache the problem and let it attempt again later to reach the nameservers.

As for the issues that caused this problem to happen in the first place, see #2030 and #2029.

Subtickets

Change History (3)

comment:1 Changed 8 years ago by shane

  • Milestone New Tasks deleted

comment:2 Changed 6 years ago by stephen

  • Milestone set to DNS Outstanding Tasks

comment:3 Changed 6 years ago by tomek

  • Resolution set to wontfix
  • Status changed from new to closed

DNS and BIND10 framework is outside of scope for Kea project.
The corresponding code has been removed from Kea git repository.
If you want to follow up on DNS or former BIND10 issues, see
http://bundy-dns.de project.

Closing ticket.

Note: See TracTickets for help on using tickets.