New DNS seeds #709

Add sipa and my DNS seeds

Only question I have is whether or not luke will use his dnsseed to get everyone connected to his eligius-relay network which has different fee rules (and whether or not that should be allowed, which is definitely arguable either way).

That was not my intention, no. It is currently a CNAME to jgarzik's DNS until I get something running.

"not my intention" doesnt answer the question...

Luke-Jr reply@reply.github.com wrote:

That was not my intention, no. It is currently a CNAME to jgarzik's DNS until I get something running.

---

Reply to this email directly or view it on GitHub: #709 (comment)

Any candidate for new DNS seeds must be well-trusted, and therefore I think a few basic tests should be applied:

1. Is the address inclusion and rotation policy well known, entirely transparent to the community? My seed is rather boring but well known: the wiki list of fallback nodes. BlueMatt's seed is the output of his published code (it is published publicly, right Matt?), etc.

2. Does the address inclusion/rotation policy intentionally favor a particular interest group (eligious relay network or whatnot)?

I would trust Luke's word if he promised the seed would always be vendor-neutral, for example.

3. Is the DNS seed setup stable, and likely to remain stable in years to come?

1. https://github.com/TheBlueMatt/dnsseed

2. Trust: as would I, hence why I asked for it.

It is vendor-neutral, which is why it is on dashjr.org instead of eligius.st. I will certainly agree to discuss it with other developers before intentionally favouring any nodes. That being said, I don't personally see any particular reason to avoid it.

As long as it discussed and publicly announced before any node-favoring is implemented and enough chance is given to disable the dnsseed in the client, that is good enough for me.