| 16 Jun 2025 |
 emily | unless the Flatpak people make some xdg-dns-portal or something that people adopt instead | 04:28:39 |
| emily | (which would be its own headache…) | 04:28:43 |
 hexa (clat on linux when) | * and for its per interface dns resolution scoping | 04:28:46 |
| hexa (clat on linux when) | yeah, glibc is a poor API, I agree | 04:29:04 |
| emily | (I wish it could do DoQ/DoH3, then I wouldn't need a separate proxy…) | 04:29:17 |
| hexa (clat on linux when) | I have no doubts that the recursor will follow | 04:29:22 |
| hexa (clat on linux when) | * I have no doubts that the recursors will follow | 04:29:37 |
| hexa (clat on linux when) | so to get back to the root of the problem | 04:30:31 |
| hexa (clat on linux when) | should systemd.network.enable also enable resolved when useLocalResolver is set? | 04:31:11 |
 @emma:rory.gay | one of my previous matrix servers made resolved crash outright | 04:31:42 |
| hexa (clat on linux when) | every local resolver uses 127.0.0.1 / ::1, resolved uses 127.0.0.53 | 04:31:44 |
| hexa (clat on linux when) | should resolved maybe just assert on useLocalResolver? | 04:32:22 |
| emily | it already asserts on resolvconf | 04:32:56 |
| emily | do you actually see fighting over resolv.conf? | 04:33:13 |
| emily | or just the local one being ignored entirely | 04:33:17 |
| hexa (clat on linux when) | one being ignored | 04:33:28 |
| emily | right | 04:33:42 |
| emily | assertion = !config.networking.useHostResolvConf;
| 04:33:43 |
| hexa (clat on linux when) | by fighting I mean kresd enabling useLocalResolver | 04:33:45 |
| @emma:rory.gay | me confingufing DNS via etc."resolv.conf" bypassing both resolved and resolvconf 👀 | 04:33:45 |
| emily | this should probably be extended | 04:33:48 |
| hexa (clat on linux when) | and not winning | 04:33:50 |
| @emma:rory.gay | * me configuring DNS via etc."resolv.conf" bypassing both resolved and resolvconf 👀 | 04:33:59 |
| hexa (clat on linux when) | so the fight is somewhere in the nixos logic | 04:34:01 |
| hexa (clat on linux when) | not necessarily in the resolvconf logic | 04:34:06 |
| emily | right | 04:34:10 |
| emily | I don't know if resolvconf + resolved is supported at all. if it's not, then the latter should probably assert on all of the former's options it doesn't implement | 04:34:26 |
| emily | hmm, resolvconf has default = !(config.environment.etc ? "resolv.conf");, but no hard assertion against enabling it anyway | 04:35:06 |
| emily | and the resolved module does networking.resolvconf.package = pkgs.systemd; | 04:35:14 |
| hexa (clat on linux when) | does resolved just bypass the module system for resolv.conf? | 04:35:20 |
