another dns scheme for yggdrasil and just clearnet ipv6 too.
so it all started with
it infers the domain from the ipv6. and that domain also can be converted back to ipv6.
the plugin was written for prosody, and it is fun, i setup an xmpp server on my pinephone, i have an account on it, and i am even able to federate with other xmpp servers that have enabled the same plugin.
folks from yggdrasil muc even managed to setup such prosody server in termux in android phones.
but this solution had a couple of problems. first, is that since your client can't resolve that v6.alt domain, you need to add to it server ip directly. if there is such a feature in the client.
secondly, the problem remains with file upload service, since again, clients cannot resolve that v6.alt domain.
so i wrote
a dns server for v6.alt domains
it listens on 53 port, responds to dns requests, converts domain name to ipv6 and returns that ipv6.
some folks from yggdrasil muc immediately started using that solution: on a computer, it can be set up to listen on localhost. but it is possible to tell it to listen on any interface, and then add that ip of that interface as dns server in yggdrasil app, so that the phone will resolve such domains.
unlike yggns or meshname, where encoded IP usually identifies the node that is authoritative for a zone, and that node runs regular DNS for its namespace, in our rn + v6.alt scheme, the encoded name itself already contains the target IPv6 address, so the resolution is much more direct and decentralized.
again, it's not my idea, it was idea of Matthew Wild, the author of the
i just decided to write a dns server for it.
Mar 29 · 6 weeks ago · 👍 ps
6 Comments ↓
📻 eugene [mod] · Mar 29 at 15:44:
One question though...
Why a new TLD when .meship does, apparently, exactly the same thing?
🐙 norayr [OP/mod] · Mar 30 at 00:10:
true, i forgot about meship.
i think because, mostly, MattJ was thinking about xmpp servers, and xmpp servers may need subdomains for mucs and file uploads, for pubsub, etc.
so in MattJ's spec if there's a subdomain, the domain is still translated to the same ip.
plus, my understanding is that the idea is to be compliant with rfc 9476.
let's say both yggns and alfis use same .ygg tld.
one of them or someone else may register such a .tld one day. so there will be a name conflict.
with .alt that should not happen because .alt is designed exactly for our use case.
🐙 norayr [OP/mod] · Mar 30 at 00:11:
still you gave me an idea, perhaps i need to add an optional meship resolver feature to rn.
📻 eugene [mod] · Mar 30 at 04:57:
Guess I'll need to hack meshnamed to also resolve .v6.alt...
🐙 norayr [OP/mod] · Mar 30 at 09:26:
are you the author?
📻 eugene [mod] · Mar 30 at 10:16:
No, but I run it for myself as part of my Lovecraftian DNS structure (dnsmasq, dnscrypt-proxy, alfis, dnsdist, meshnamed...) so might as well send in a PR, should only be a few lines.