Closed Bug 1692494 Opened 3 years ago Closed 3 years ago

TRR_NXDOMAIN no longer recorded when 0x03 rcode is set in the TRR response header

Categories

(Core :: Networking: DNS, defect, P2)

Product:
Core
Component:
Networking: DNS
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Milestone:
88 Branch
Tracking Flags:
Tracking Status
firefox-esr78 --- unaffected
firefox85 --- unaffected
firefox86 --- unaffected
firefox87 --- wontfix
firefox88 --- fixed

People

(Reporter: nhnt11, Assigned: valentin)

References

(Regression)

Details

(Keywords: regression, Whiteboard: [necko-triaged])

Attachments

(1 file)

Bug 1692494 - TRR_NXDOMAIN no longer recorded when 0x03 rcode is set in the TRR response header r=nhnt11
48 bytes, text/x-phabricator-request
Details | Review

I think this was a rebase issue; the line that sets TRR_NXDOMAIN skip reason was removed. Just need to add it back I think.

Severity: -- → S4
Priority: -- → P2
Whiteboard: [necko-triaged]

Set release status flags based on info from the regressing bug 1691721

status-firefox85: --- → unaffected
status-firefox86: --- → unaffected
status-firefox87: --- → affected
status-firefox-esr78: --- → unaffected
Assignee: nobody → valentin.gosu
Status: NEW → ASSIGNED

Can we add a test for this?

Flags: needinfo?(valentin.gosu)
Flags: in-testsuite?
Pushed by valentin.gosu@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/4d235b30c5ee
TRR_NXDOMAIN no longer recorded when 0x03 rcode is set in the TRR response header r=nhnt11

https://hg.mozilla.org/mozilla-central/rev/4d235b30c5ee

Status: ASSIGNED → RESOLVED
Closed: 3 years ago
status-firefox88: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 88 Branch

Do we want this fix in 87? Please request uplift if so.

I think we can let it ride the trains - there are some conflicts to uplifting.

Flags: needinfo?(valentin.gosu)
Has Regression Range: --- → yes
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: