Discuss mailing list

[Coyo <coyo AT darkdna.net>]

http://tools.ietf.org/html/draft-grothoff-iesg-special-use-p2p-names-00

Since this will almost certainly not pass, I was wondering what you guys thought of me running DNS servers that resolved P2P-related domain names?

For Tor's .onion pTLD, it could operate much like onion.to does, as an in-proxy, as I2P would call it, clearnet gateway in tor parlance, while .i2p would function similarly, as an inproxy. If anyone wanted to donate in-proxy services, the .onion and .i2p TLDs could point to a selection of IPv4 and IPv6 reverse proxies (nginx, haproxy, or varnish) which would forward the connection to the appropriate eepsite or hidden service.

It would be a public service much like pool.ntp.org.

The .exit pTLD would be handled similarly, providing a sort of web proxy in effect.

Similar behavior with .gnu and .zkey, with gnunet as the overlay in question. See https://gnunet.org/faq-page#t34n1852 for details. The .zkey pTLD would return the PKEY record as expected. Due to the inherent complexity of managing stateful tables mapping tcp connections and udp sessions to remote services transparently, the ports that are port-network address translated are limited to common services such as XMPP, IRC, SMTP and HTTP. Initially, only HTTP connections may be accepted to reduce NAT-related complexity.

What do you guys think? If anyone would do this, it would probably be me. It would give me an excuse to play with powerdns.