http://en.wikipedia.org/wiki/Round-robin_DNS
The goal is to place Hidden Service in multiple data centers to prevent
single point of failure.
--
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinf
D A can i speak with you in private? greg
Greg Curcio
On Sat, Sep 27, 2014 at 10:42 PM, Dmitry Alexandrov
wrote:
> http://en.wikipedia.org/wiki/Round-robin_DNS
>
> The goal is to place Hidden Service in multiple data centers to prevent
> single point of failure.
> --
> tor-talk mailing list -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/28/2014 12:42 AM, Dmitry Alexandrov wrote:
> http://en.wikipedia.org/wiki/Round-robin_DNS
>
> The goal is to place Hidden Service in multiple data centers to
> prevent single point of failure.
>
Namecoin would make this pretty easy. Last I ch
Dmitry Alexandrov writes:
> http://en.wikipedia.org/wiki/Round-robin_DNS
>
> The goal is to place Hidden Service in multiple data centers to prevent
> single point of failure.
It's not so easy (to implement something like Round Robin DNS for
HSes). It requires complicated protocol modifications.
; To: tor-talk@lists.torproject.org
> Subject: [tor-talk] Hidden Services - how to implement something like Round
> Robin DNS?
>
> http://en.wikipedia.org/wiki/Round-robin_DNS
>
> The goal is to place Hidden Service in multiple data centers to prevent
> single point of fai
; To: tor-talk@lists.torproject.org
> Subject: Re: [tor-talk] Hidden Services - how to implement something like
> Round Robin DNS?
>
> D A can i speak with you in private? greg
>
> Greg Curcio
>
> On Sat, Sep 27, 2014 at 10:42 PM, Dmitry Alexandrov
> wrote:
>
m
> To: tor-talk@lists.torproject.org
> Subject: Re: [tor-talk] Hidden Services - how to implement something like
> Round Robin DNS?
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 09/28/2014 12:42 AM, Dmitry Alexandrov wrote:
> > http://en.wikipedia.org/wiki/
On 9/27/14, Jeremy Rand wrote:
> ...
> Namecoin would make this pretty easy. Last I checked the current
> Namecoin domain name spec only supports round-robin DNS for IPv4/IPv6
> and not Tor/I2P, but there's consensus that that will be changed soon
> to allow round-robin for Tor and I2P as well.
If all you want to do is load share right now today,
you can set the main onion to 302 all traffic amongst
an onion farm. It's only for http and isn't perfect but
it does spread the traffic around.
--
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/30/2014 05:28 PM, coderman wrote:
> On 9/27/14, Jeremy Rand wrote:
>> ... Namecoin would make this pretty easy. Last I checked the
>> current Namecoin domain name spec only supports round-robin DNS
>> for IPv4/IPv6 and not Tor/I2P, but there's
On 10/5/14, Jeremy Rand wrote:
> ...
> Any chance you could provide more details on what you're using? Last
> I heard the only Namecoin resolvers that handle Tor/I2P services were
> FreeSpeechMe and NMCSocks; FreeSpeechMe doesn't handle round-robin,
> and I'm pretty sure NMCSocks doesn't either.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
A distributed list would help the scalability of the network and could
evolve to substitute the 9 mian directory authority servers. What
about some sort of lottery system of say 900 auth dir's on a list that
is edited every time it is transmitted?
12 matches
Mail list logo
