Closed Bug 1696446 Opened 4 years ago Closed 4 years ago

Don't set CONFIRM_FAIL until we actually complete a confirmation attempt, when we see multiple consecutive failures

Categories

(Core :: Networking: DNS, enhancement, P1)

Product:
Core
Component:
Networking: DNS
Type:
enhancement

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1658278

People

(Reporter: nhnt11, Assigned: nhnt11)

References

Details

(Whiteboard: [necko-triaged])

According to our new state flow [1] we should go into the TRY-OK state when we see multiple consecutive failures. In this state, we attempt a fresh confirmation but we still allow TRR lookups, until that attempt fails (at which point we go into TRY-FAIL).

[1] bug 1658278 comment 1

Assignee: nobody → nhnt11
Status: NEW → ASSIGNED

I didn't realize that Valentin is working on this already in bug 1658278. 🙂

Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.