[dashninja.pl] Dash Masternode Ninja - Free Masternode Monitoring

elbereth

Active Member
Dash Support Group
Mar 25, 2014
440
466
133
Costa Rica
dashninja.pl
Dash Address
XkfkHqMnhvQovo7kXQjvnNiFnQhRNZYCsz
There is since 2 weeks an intermittent DNSSEC failure on DashNinja.pl domain (no idea why as everything is configured correctly and worked for years). This result in the website been not accessible if you DNS resolver checks for DNSSEC validation (they should...).

Trying to fix that problem on dashninja.pl (it will take at least 48h, restarting the OpenDNSSEC config from scratch), in the meantime you can :
1) disable DNSSEC verification (if you have a local bind allowing that) - Not recommended
2) use TOR v2 : http://seuhd5sihasshuqh.onion/masternodes.html
3) use TOR v3 : http://dtsfpvtrnqcyordz62efdrvhevgmqvpi5ora2nul7c2wikjxw5kboeqd.onion/masternodes.html
4) use I2P : http://dzjzoefy7fx57h5xkdknikvfv3ckbxu2bx5wryn6taud343g2jma.b32.i2p/masternodes.html (or http://dashninja.i2p/masternodes.html if you put it in your adress book)
5) use the alternative URL (HTTPS too, same server, just using a subdomain of my personal domain) : https://dashninja.elbereth.zone/
 

elbereth

Active Member
Dash Support Group
Mar 25, 2014
440
466
133
Costa Rica
dashninja.pl
Dash Address
XkfkHqMnhvQovo7kXQjvnNiFnQhRNZYCsz
Normal URL should be fixed.
Additionally masternode/governance listing was stuck for 4 days. Fixed too.
 

daf

Active Member
Oct 18, 2015
176
133
103
Hi @elbereth , is there an API for getting info about deterministic MNs? (Registration block, last paid block, penalty, etc.)
 

qwizzie

Well-known Member
Aug 6, 2014
1,581
737
183
There is since 2 weeks an intermittent DNSSEC failure on DashNinja.pl domain (no idea why as everything is configured correctly and worked for years). This result in the website been not accessible if you DNS resolver checks for DNSSEC validation (they should...).

Trying to fix that problem on dashninja.pl (it will take at least 48h, restarting the OpenDNSSEC config from scratch), in the meantime you can :
1) disable DNSSEC verification (if you have a local bind allowing that) - Not recommended
2) use TOR v2 : http://seuhd5sihasshuqh.onion/masternodes.html
3) use TOR v3 : http://dtsfpvtrnqcyordz62efdrvhevgmqvpi5ora2nul7c2wikjxw5kboeqd.onion/masternodes.html
4) use I2P : http://dzjzoefy7fx57h5xkdknikvfv3ckbxu2bx5wryn6taud343g2jma.b32.i2p/masternodes.html (or http://dashninja.i2p/masternodes.html if you put it in your adress book)
5) use the alternative URL (HTTPS too, same server, just using a subdomain of my personal domain) : https://dashninja.elbereth.zone/
Dashninja seems broken since yesterday, both the normal dashninja deterministic site and the elbereth.zone site, are you aware of this and perhaps
in the middle of some maintenance ?
 

qwizzie

Well-known Member
Aug 6, 2014
1,581
737
183
Hi @elbereth ,

Looks like dashninja is getting a lot of false 'port closed' signals ? All my masternodes are on 'port closed', while i am pretty sure they have open ports.
They also stay on 'port closed' after each port check.

My masternodes have been updated to v0.16.0.1 and show just fine on Dash Central.
I think this started to happen after my update to v0.16.0.1

[Your node can be shown as closed but be working fine, the port scanner can be banned by your node for 24h]
Maybe this is happening ? Just strange that it happens to all my nodes at the same time.
 
Last edited: