Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • C Chutney
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 44
    • Issues 44
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • Chutney
  • Issues
  • #21632
Closed
Open
Created Mar 04, 2017 by teor@teor

"Couldn't set up any working nameservers. Network not up yet? Will try again soon."

When DNS fails, chutney can't verify any networks involving exits. This is really annoying on a plane, or for those who like to develop without a network connection.

We have 3 options here:

  • configure chutney to allow broken DNS
  • modify Tor to allow broken DNS in test networks
  • add a fake DNS server (legacy/trac#19573 (moved))

Assigning this ticket to chutney until I'm sure we can't fix it by changing the torrc templates.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking