Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
R
respdiff
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 19
    • Issues 19
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 3
    • Merge Requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Knot projects
  • respdiff
  • Issues
  • #10

Closed
Open
Created Nov 22, 2017 by Petr Špaček@pspacekContributor0 of 3 tasks completed0/3 tasks

support blacklisting in results

Some queries/domains might be broken on the remote end, which should be detected when resolver-benchmarking#19 is implemented.

Once we have information that particular domain is broken on remote end, we should generate a blacklist so the domain does not show up again in subsequent analysis.

Example:

== Global statistics
queries             100000
answers             100000    100.00 % of queries
blacklisted answers    100      0.10 % of answers (analyzing 99.90 % of answers)
others agree         99000     99.10 % of analyzed answers (ignoring 0.90 %)
target diagrees        500      0.51 % of matching answers from others

Detailed reports should not include blacklisted domains.

Open question is how we should do the blacklisting:

  • by domain name
  • by domain sub-tree
  • by name servers (this might require additonal DNS queries just to find out NS set)
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None