This was explained by Fluffypony on Reddit:
It says "warning", so it's not an error, it's just a notice:)
MoneroPulse is informational only, unless you're running an unmanaged node and you've thus set the flag to explicitly follow MoneroPulse checkpoints. Currently there are three things to note with MoneroPulse:
- moneropulse.co is having issues, it's in the process of being moved to a different registrar. BUT moneropulse.org, moneropulse.net, and moneropulse.se are all fine and pass DNSSEC validation, so finding 2 working ones is not that hard.
moneropulse.co is having issues, it's in the process of being moved to a different registrar. BUT moneropulse.org, moneropulse.net, and moneropulse.se are all fine and pass DNSSEC validation, so finding 2 working ones is not that hard.
We're having issues with our baked-in root trust anchor for systems that don't have trust anchors. You may have noticed a message on startup complaining about "unsupported algorithm for trust anchor . DNSKEY IN" - we have a new format for the baked-in anchor that should fix this, but it's not part of 0.9 or 0.9.1.
Even if 1 and 2 are perfect and resolved there are some ISPs that run DNS servers that don't acknowledge the +dnssec flag when making requests, so there are some environments where you're never going to get a valid MoneroPulse response. That's why MoneroPulse is just informational only:)
- We're having issues with our baked-in root trust anchor for systems that don't have trust anchors. You may have noticed a message on startup complaining about "unsupported algorithm for trust anchor . DNSKEY IN" - we have a new format for the baked-in anchor that should fix this, but it's not part of 0.9 or 0.9.1.
- Even if 1 and 2 are perfect and resolved there are some ISPs that run DNS servers that don't acknowledge the +dnssec flag when making requests, so there are some environments where you're never going to get a valid MoneroPulse response. That's why MoneroPulse is just informational only:)
