GitLab

Go beyond the capabilities of the current address result handling by
allowing results in any order, as long as it creates a complete chain
from query name to the result name(s).  The ordering requirement used in
the current-but-quickly-becoming-legacy address result handling is
generally followed by the DNS ecosystem, but as far as I can tell, not
officially required by any spec.  Plus, we will soon start allowing
similar HTTPS aliasing, which will not require any specific response
ordering.

Bug: 1147247,640596
Change-Id: Id10767d34a2c638b142123145cd41dfe0dee0fd0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2532514Reviewed-by: Matt Menke <mmenke@chromium.org>
Commit-Queue: Eric Orth <ericorth@chromium.org>
Cr-Commit-Position: refs/heads/master@{#828595}