Future of DNS/TLD - Githubissues

freifunk-berlin / meta

Selbstorganisierung der Berliner Freifunk Community

https://berlin.freifunk.net

0 stars 0 forks source link

Future of DNS/TLD #7

Open noxilixon opened 1 year ago

noxilixon commented 1 year ago

How do we solve DNS while we migrate from olsrd to babel? Which TLD should we use in the future?

nicolasberens commented 10 months ago

Since only these TLDs are reserved: https://datatracker.ietf.org/doc/html/rfc2606#section-2

.test
.example
.invalid
.localhost

We should either use one of those or a "real" domain.

E.g. $service.internal.berlin.freifunk.net

Pro rfc2606:

no overloading if someone decides to register the .olsr TLD

Con rfc2606:

all of them don't make "sense" in our context and look weird

Pro Real:

looks better, $service.internal.berlin.freifunk.net or $service.freifunk.berlin "looks real" to normal users Con Real:
who is the owner?
Wat if someone hosts illegal stuff and the law knocks on your door

This "might" lead to problems if someones distributes

noxilixon commented 9 months ago

Pro Real:

We could create a service to make the mesh internal services available from the outside. This service will forward only accepted services from the mesh to the internet, so that we don't have the problem with illegal content. Mesh internal services could still be created and accessed without being accepted.

I would propose $service.ff.berlin as domain, because it is short, easy to remember and already in the hands of the community. Owner should be the legal entity of the community that is still to be created.

adam-burns commented 2 months ago

Pro Real:

Back in May, we presented sig0namectl at the Freifunk Berlin monthly meetup. sig0namectl allows secure, decentralized DNS update capabilities within Freifunk (for those that wish to use it).

Since then, we've achieved quite a few milestones:

for strong integrity of resolver interactions we have enabled DNSSEC on freifunk.net & berlin.freifunk.net zones.
we have been running beta testing of SIG(0) key registration for fully decentralized, secure DNS updates (for both routers and endpoint hosts) under the beta.freifunk.net DNS zone for some months & about to open beta.berlin.freifunk.net

With respect to both internal (& soon optional externally) available services, we have been testing Wide Area DNS Service Discovery, which offers more interoperability and flexibility of service types than a single 'service' label.

For more information on the current status and capabilities of this project, see the sig0 website and github repo.

Noki commented 2 months ago

.internal is now reserved as well and intended for internal use: https://www.icann.org/en/announcements/details/icann-seeks-feedback-on-proposed-top-level-domain-string-for-private-use-24-01-2024-en