-
Couldn't load subscription status.
- Fork 44
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Expected Behavior
Users should be able to connect to thenetwork using latest SDK as provided by documentation
Current Behavior
Mainnet seeds are not working. When you install SDK from the npm, it fails to sync and fails silently for the user, because there are no error handlers implemented, it just keeps syncing forever.
If you raise the log level via envrionment, you can see a message:
debug: [DAPIClient: 151ca6f784] [ReconnectableStream] Error handler 14 UNAVAILABLE: Name resolution failed for target dns:seed-3.mainnet.networks.dash.org Error: 14 UNAVAILABLE: Name resolution failed for target dns:seed-3.mainnet.networks.dash.org
Telnet is also not possible on the seed address.
pshenmic@Mikhails-MacBook-Pro ~ % telnet seed-3.mainnet.networks.dash.org 26656
seed-3.mainnet.networks.dash.org: nodename nor servname provided, or not known
This is very important because it highly affecting people's performance and confusing them. Its not easy to insert an IP manually too, because you need to know where to grab it beforehand.
Possible Solution
Steps to Reproduce (for bugs)
Context
Your Environment
- Version used:
- Environment name and version (e.g. Chrome 39, node.js 5.4):
- Operating System and version (desktop, server, or mobile):
- Link to your project:
kxcd and riongull
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working
Type
Projects
Status
In Progress