Run a diagnostic experiment to determine the impact of order/cache warming on failures #65
Comments
k88hudson
added a commit
to k88hudson/mozilla-pipeline-schemas
that referenced
this issue
Feb 24, 2023
k88hudson
added a commit
to k88hudson/mozilla-pipeline-schemas
that referenced
this issue
Feb 25, 2023
k88hudson
added a commit
to k88hudson/mozilla-pipeline-schemas
that referenced
this issue
Feb 26, 2023
fbertsch
added a commit
to mozilla-services/mozilla-pipeline-schemas
that referenced
this issue
Feb 26, 2023
* Add changes for DNSSEC experiment v8 See mozilla-extensions/dnssec-interference#65 * Changes for DNSSEC experiment v8 part 2 See mozilla-extensions/dnssec-interference#65 * Render DNSSEC v8 schema --------- Co-authored-by: Frank Bertsch <frank.bertsch@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Specifically we want to check if recursive resolvers are caching responses for A requests that are incorrectly used to respond to our custom range record queries. This involves adding some queries for domains in various orders (A first, NEWONE first, etc.)
We also want to capture order and timestamp information in a new section of the payload,
dnsQueryInfoThe text was updated successfully, but these errors were encountered: