NixOS Networking | 900 Members | |
| Declaratively manage your switching, routing, wireless, tunneling and more. | 261 Servers |
| Sender | Message | Time |
|---|---|---|
| 12 Sep 2025 | ||
| 03:27:06 | ||
| 03:34:46 | ||
| Katalin 🔪: toonn what do you think about switching from tailscale to zerotier in this case? | 10:26:18 | |
| Don't have experience with Zerotier. It sounds more open but I don't have reliable publically accessible hardware for relaying and such. | 10:35:03 | |
| 12:47:05 | ||
| ghostbuster91: As promised my unicast DNS multicaster, https://codeberg.org/toonn/dns2mdns | 13:15:30 | |
| Huh? Doesn't nginx support resolving through normal OS provided name lookups? | 13:32:35 | |
| If you have a configuration for me that makes that utility redundant, I'm all ears. | 13:37:14 | |
| @toonn:matrix.org some haskell review
| 13:37:15 | |
| You can enable mDNS in systemd-resolved and then nginx should use that. | 13:37:49 | |
| I have that kind of setup somewhere. There's some shitty behaviors with the systemd-resolved mdns implementation relating to IPv6, but I don't remember what exactly was the pain point with that. It was something they specifically defined to do wrong and not care about, if I remember correctly. | 13:40:36 | |
| I had this on one laptop where I absolutely needed to use network damager for managing WiFi due to reasons. Thus, the rather weird config on that.
| 13:44:51 | |
| Firewall needs to be handled as well, like:
| 13:45:31 | |
| so systemd-networkd is used to manage all other network things except WiFi, and systemd-resolved is used for all DNS lookups | 13:47:47 | |
| Oh, you know what, I think I remember what the problem with systemd-resolved is in my case. It doesn't allow for subdomains of .local! | 13:51:57 | |
| That's out of spec | 13:52:15 | |
|
| 13:52:23 | |
| Yep, and working well for me : ) | 13:52:26 | |
| I really don't see a good reason for it to be out of spec, it's just an arbitrary decision AFAICT. | 13:53:07 | |
| Ahh. Well, that is a use case I have not had. :D | 13:53:13 | |
Does the spec restrict valid TLDs? .local is very very common | 13:57:29 | |
| I think the spec requires .local actually. | 13:57:51 | |
| No, but the mDNS spec does not allow multiple parts in the domain name | 13:58:17 | |
| It does require .local | 13:58:36 | |
| But foo.bar.local is not allow | 13:58:42 | |
| * But foo.bar.local is not allowed | 13:58:45 | |
| Only foo.local | 13:58:48 | |
| Oh, so no subdomains | 13:59:14 | |
| Weird | 13:59:16 | |
| I assume it's because some printer's implementation somewhere splits on the first `.` and then proceeds to freak out. | 13:59:56 | |