According to all known laws of DNS, there is no way a fedi instance could be hosted on an .ARPA domain.
Even if you get ahold of a domain like this, it should only be used for PTR records - right?
The instance, of course, federates anyway - because DNS doesn't care what humans think is impossible.
@domi this is amazing.
@loke @domi A really, really bad idea. As someone who worked at the first site on the early ARPANET at UCLA and worked on the original ARPANET protocols and continuously going forward from then, I assure you that doing this will cause you nothing but grief down the line. You can play games with DNS but eventually you'll get bitten. Trust me on this.
@lauren @loke @domi I've run fairly large authoritative dns deployment, I've hacked in the protocol in various ways.
The only concern is if the block allocation is pulled, but this a RIR/LIR concern.
There is nothing in the protocol that would consider this a violation. At the end of the day, this is straight up NS delegation. Is this unusual? yes. Is this humanly possible to remember an ipv6 block allocation? No, not in a large scale, this is the reason for DNS in the first place, but that's it?
@kkarhan @baloo @lauren @loke @domi speaking of…”unconventional” TLDs for individuals to have, back near the turn of the century (2000-01 or so i think), I knew of someone who had a .edu domain for their personal website. I’m not entirely sure how they pulled it off, I guess the eligibility criteria were enforced mostly by the honor system at the time that they registered it
@maia @kkarhan @lauren @loke @domi edu registration was just a single person maintaining it for a very long time. And you'd email them to have a domain on it.
They had a bunch of made-up rules, like the length was to be kept under 8 chars.
My partner works at a museum that would have violated that rule, when they applied in the early 90s. They just waived the rule for them.
Yeah, honor-system, mild enforcement, or just feeling based.
@filmroellchen@donotsta.re@lauren @loke @domi that’s funny, you’re taking the internet seriously, you’re taking internet engineering seriously. lol. this isn’t even against the rules. these domains are delegated like anything else, they just often don’t point to AAAA/A records. rfcs are guidelines, not rules. rfcs just say what your PTR record has to be, not what your AAAA record can be.
did you know @ruhrscholz played videos over TXT records before? it broke powerdns, but they even accepted the patches to fix it
@f2k1de@cuties.social@filmroellchen @domi @loke @lauren @ruhrscholz you can use TXT records even as a VPN :D
@filmroellchen @domi @loke @ruhrscholz Where did I say anything about rules? I never mentioned the word. All I said is that depending on these kinds of "tricks" is looking for trouble. And I stand by that. I've had to help a large number of people undo the messes they've created over the years trying to be "creative" in DNS records. But hey, pick your poison.
@filmroellchen@donotsta.relol
@lauren @filmroellchen @domi @loke hey can you share some details on the upcoming ""trouble"" please? (:
also:
dig @1.1 +short TXT {0..92}.vid.demo.servfail.network | sed 's/[" ]*//g' | base64 -d | ffplay -
@merlin @filmroellchen @domi @loke You can enjoy the thrill of discovery in due time. Have fun!
@lauren @merlin @filmroellchen @domi @loke
This is an entertaining hack. The _fun_ kind of FAFO.
Could even help expose bugs and get them fixed. Socially beneficial FAFO?
@lauren @domi I'm pretty sure the owner of the instance knows as well. In the description it is mentioned that it'll only be up for a month.
I was just surprised it worked. But of course, thinking about how DNS works, it makes sense. Good idea? Absolutely not. But it's a cool experiment that teaches us a bit about DNS I think.
@loke @domi Sure, experimentation can be fine so long as it is not going to negatively impact other systems. But it's always useful to keep in mind the distinction between experimental and production configurations. I will add that "unusual" domain configurations stand a very high chance of being blocked or tagged as problematic in the long run. And once you get on those block lists, getting off again can be, shall we say, challenging, because there is often an assumption -- not without considerable merit -- that oddball configurations and "creepy" DNS entries are attempting to bypass spam/phishing/malware blocking systems and filters -- which is not infrequently the case.
