Skip to content

Should listen to ports right after finding right amount of servers #2926

@7c

Description

@7c

Imagine following scenario:

  • linux host is under censorship country
  • public-resolvers contains over 100+ public-resolvers, somehow the .md file is shipped alongside the configuration as cache
  • because we dont know which servers are blocked or will be blocked soon, we cannot set 'server_names' parameter, so leaving it empty will start a 'network test'
  • the 'network tests' takes 6 full minute and around 40 possible working servers found
  • then DNSCrypt starts listening to mentioned port(s) and outputs 'dnscrypt-proxy is ready - live servers: 40'

in such a setup those 6 minutes server will be without resolv. It should be possible to change the lb strategy to something like 'quick4' where it launches the listen operations after finding 4 servers. I could not find such a feature. We do not know which servers will be blocked next hours, so keeping 'server_names' not set is only option to find server

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions