New issue
Advanced search Search tips

Issue 794258 link

Starred by 3 users
Status: Untriaged
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: Android , Chrome , Mac
Pri: 3
Type: Bug



Sign in to add a comment

DnsTask can combine results for two different fully qualified names

Project Member Reported by mge...@chromium.org, Dec 12 2017 
If there are multiple entries on the search list, it's possible for the A transaction to return results for one name while the AAAA query returns results for another. DnsTask can't detect this, so it will just combine the two. The cases where this would happen are all kind of broken anyway, but it seems like the wrong way to handle the situation.

One potential fix is moving the search list handling into DnsTask, which would also help with issue 779589.

Comment 1 by mmenke@chromium.org, Dec 12 2017 

Oops.  I think I broke this when I made A and AAAA queries run in parallel.  It looks like if we handle them sequentially, we do things correctly?  Or at least we start with the suffix-matched hostname (Not sure if it always ends in a dot, to prevent another suffix search, or not)
Project Member

Comment 2 by sheriffbot@chromium.org, Dec 13

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 3 by marcuskoehler@chromium.org, Jan 15

Labels: Enterprise-Triaged
►

Sign in to add a comment