Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
R
respdiff
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 18
    • Issues 18
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 2
    • Merge Requests 2
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Registry
    • Registry
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Knot projects
  • respdiff
  • Issues
  • #31

Closed
Open
Opened Jan 14, 2019 by Tomas Krizek@tkrizek
  • Report abuse
  • New issue
Report abuse New issue

dnsviz: make the tool more robust

dnsviz itself is prone to random tracebacks or even deadlocks.

When used to analyze multiple domains at once (-f), in multiple threads (-t), even one such failure will cause the entire process to fail.

Even though it's slower and less efficient, the analysis will be more resilient if dnsviz is used to verify a single domain only, one at a time (and with a timeout for the command). The parallelization should take place in our code.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
No due date
0
Labels
None
Assign labels
  • View project labels
Reference: knot/respdiff#31