Modlog - Divisions by zero
lemmy.dbzer0.com

Dafuck? Removed for rule 3? !selfhosted@lemmy.world what the?

As far as I’m aware running and getting DNS to work on a home network is precisely everything to do with self-hosting.

I get that I’m being a bit of an opinionated asshole, and maybe my post is not overly constructive, but shit, a good rant to start a discussion should not be a reason for removal, least of all for a rule that has blatantly not been violated and that’s the only actual reason I can think of why I’d been banned.

A good rant is literally the most worthwhile content imho, a good hearty debate invites viewpoints and opinions, even if the OP is unpopular. I hate the sterile, overly polite, overly PC tone enforced on some Lemmy communities.

As long as no one is literally insulting other users or spreading misinformation or being discriminatory/xenophobic based on characteristics. I wasn’t even swearing. I’m so done, I’m blocking all of lemmy.world until they get their shit together.

  • LainTrain@lemmy.dbzer0.comOP
    12·
    2 days ago

    Is .local actually “commonly used for local domains in LAN DNS”

    Yes. It was even the suggested practice at one time:

    https://en.m.wikipedia.org/wiki/.local

    At one time, Microsoft at least suggested the use of .local as a pseudo-TLD for small private networks with internal DNS servers

    Using the .local label for the full DNS name for the internal domain is a more secure configuration because the .local label is not registered for use on the Internet. This separates your internal domain from your public Internet domain name.

    By default, a freshly installed Windows Server 2016 Essentials also adds .local as the default dns-prefix when a user doesn’t select the advanced option, resulting in a domain with .local extension.

    Yes they retracted the recommendation later, but in reality there are hundreds of thousands of networks that still use it. On the other hand almost nothing uses mDNS.

    fyi, besides Android, most Linux distros also ship with mDNS enabled by default, as do all Apple operating systems since the feature was first introduced in an update to Mac OS 9 in 2001. It’s mostly just Windows that doesn’t.

    FYI, the behaviour of resolving .local domains ONLY VIA MDNS is exclusive to android.

    On the other hand, Windows of course does indeed have mDNS out of the box, same as Linux, per the RFC.

    Are you removed, or just pretending? Fucking bootcampers istg I’m so glad I don’t have to work with y’all and only interact when you deliver my fucking takeaway.

    Which RFC says that?

    You would know if you could fucking read as it’s linked pretty clearly in my post:

    https://support.google.com/pixelphone/thread/139593141?hl=en&msgid=149988130

    Links to:

    https://www.rfc-editor.org/rfc/rfc6762.html#section-6

    Which is RFC 6762, which says:

    Implementers MAY choose to look up such names concurrently via other mechanisms (e.g., Unicast DNS) and coalesce the results in some fashion

    So actually the RFC does not limit whatsoever the resolution of .local domains to mDNS. Implementers, apart from Android do indeed always do look up via both unicast and multicast (if not disabled). Only android limits this to multicast-only.

    Also, as per (the immediately prior) RFC6761 (“Special-Use Domain Names”), RFC6762 explicitly adds .local to the IANA registry of special-use domain names.

    So? This has nothing to do with android’s bizarre limitation on how it resolves .local.

    HTH! KYS BTW!

    • Arthur BesseAEnglish
      3·
      2 days ago

      Yes. It was even the suggested practice at one time:

      https://en.m.wikipedia.org/wiki/.local

      Cool, I didn’t know that. But the article also says they recommend against it now. I see the “Microsoft recommendations” section of the wikipedia article indicates they changed their mind on this several times.

      On the other hand almost nothing uses mDNS.

      In my experience mDNS seems ubiquitous; almost every network connected device I’ve seen in the last couple decades has it enabled by default.

      Fucking bootcampers istg I’m so glad I don’t have to work with y’all and only interact when you deliver my fucking takeaway.

      Huh? What are “bootcampers”? It used to refer to people running windows on intel macs (because apple’s boot loader to allow that was called BootCamp), but that wouldn’t make any sense in this context. Unless you are having your food delivered by people who run Windows on old Apple hardware? 🤔

      Implementers MAY choose to look up such names concurrently via other mechanisms (e.g., Unicast DNS) and coalesce the results in some fashion

      So actually the RFC does not limit whatsoever the resolution of .local domains to mDNS. Implementers, apart from Android do indeed always do look up via both unicast and multicast (if not disabled). Only android limits this to multicast-only.

      I see. Sorry I missed that part of the RFC.

      But, FYI, it is really not only Android that doesn’t send unicast queries for .local names; GNU/Linux distributions running avahi (eg, the distros most people use) also don’t. I don’t have a mac or iphone nearby to confirm but I would assume they are probably resolving .local exclusively via mDNS too. edit: this “Apple devices might not open your internal network’s ‘.local’ domain” support article indicates my assumption is probably correct.

      Also, please don’t tell people to KYS :(

      • LainTrain@lemmy.dbzer0.comOP
        2·
        2 days ago

        In my experience mDNS seems ubiquitous; almost every network connected device I’ve seen in the last couple decades has it enabled by default.

        Again, having it enabled by default is not an issue. I have it enabled everywhere, as you said - it’s the default. But, it’s also the default that .local is resolved both via multicast and unicast.

        But, FYI, it is really not only Android that doesn’t send unicast queries for .local names; GNU/Linux distributions running avahi (eg, the distros most people use) also don’t.

        Yes they do? Well at least in my case they do. As far as Unix/Linux I have Raspbian, Debian, OpenBSD, OpenWRT, SteamOS (had to hand-wring the DNS there tbf), Ubuntu, Mac OS and Kali and they all resolve just fine. I run my own recursive DNS server for internet and an authoritative zone for my local DNS, a domain ending in .local, and they all resolve .local via my server as is given to them by DHCP.

        The Pi is definitely running Avahi and spamming multicast, when it attempts to resolve .local, it sends out multicast and unicast simultaneously, even with freshly flushed DNS cache.

        But the article also says they recommend against it now.

        That is very new though. .local is still default on fairly recent versions of Winserver (2016), as that article also specifies. I can attest this is also commonly still used by large businesses who don’t want their AD to be related to their TLDs, RFC or no RFC, which makes the android implementation all the more idiotic.

        Don’t tell people to KYS

        Okay. I got a fuckload of insults and dismissal from peabrains ITT in comments above yours, so I may have gone too far in a few places.

        • Arthur BesseAEnglish
          3·
          2 days ago

          The Pi is definitely running Avahi and spamming multicast, when it attempts to resolve .local, it sends out multicast and unicast simultaneously, even with freshly flushed DNS cache.

          I owe you an apology - I see now that my avahi systems are in fact also sending unicast SOA? local. when I resolve a .local name, and presumably if my recursor told them it was responsible for it instead of NXDomain then I would resolve names through it.

          I was pretty sure that it doesn’t do that, but before telling you that it doesn’t I actually did a test and ran tcpdump -ni any port 53 or port 5353 while resolving some .local names. i even noticed that there was that SOA query being sent to and from localhost (to systemd-resolved) but I saw no answer to it and figured that systemd-resolved was the thing silently ignoring that TLD. But: it turns out that the system I tested on has its systemd-resolved configured for DNSOverTLS so I wasn’t seeing those SOA queries being sent on to the recursor on a different port 🤦

          Sorry!

          It does seem to me like a regrettable choice of the RFC authors to allow both, though, as it is easy to accidentally have a situation where the recursor and mDNS return different answers which would lead to inconsistent results when querying both in parallel.