git ssb


ansuz / dnssb

Tree: 430f06d7898e5850d1c1eaac6802a6fe97590c4f

Files: 430f06d7898e5850d1c1eaac6802a6fe97590c4f / docs /

2260 bytesRaw

Frequently Asked Questions

Can I use this without running scuttlebot?

You could get a friend to host dnssb for you if you really trust them and don't care if they see all your dns requests. Once running, you should be able to use the dns server as you would any other dns provider.

Is it Enterprise-Ready?

That depends on your the needs of your Enterprise, but I would lean towards no.

Does it protect against name-squatting?

The records available to dnssb are sourced from your ssb social network, so the quality of your results will depend on who you choose to follow (and who they choose to follow).

How can I deal with malicious behaviour?

Records must be published by someone in your social network, and all such records are cryptographically signed using their private key.

If you notice malicious behaviour, it can always be traced back to the person who published it, through your social graph, if need be. Naming things is a social problem, and the best way to resolve conflicts is probably to discuss it.

Additionally, in the future there will be better support for reporting and blocking abusive behaviour.

How does it handle multiple records for a single domain?

Records are concatenated together, even if they are authored by different users.

Does it resolve conflicts if they occur?

Since multiple publish actions are concatenated together, the only way to conflict is for two users to update the same message. In such a case, the previous set of records will be replaced with the set of all records which attempted to replace it.

What is it good for?

  1. If there is a DNS outage you can still resolve any records you or your friends have published to ssb.
  2. As with everything committed to ssb, records are stored locally (and indefinitely) in a set of hash chains (one for each user). As such, if you don't have access to the internet at all, this will continue to work
  3. You can use this as a kind of distributed hosts file

How optimized is this?

Not much, but it should get better over time if people are interested in using it.

Is there a web interface?

Not yet, but I'd like there to be!

Does it handle wildcard entries?

Not yet, but I'd like it to!

Built with git-ssb-web