!tCyGickeVqkHsYjWnh:nixos.org

NixOS Networking

914 Members
Declaratively manage your switching, routing, wireless, tunneling and more.265 Servers

Load older messages


SenderMessageTime
16 Jun 2025
@hexa:lossy.networkhexahttps://github.com/NixOS/infra/commit/67eb34a7534e9caeda495fbbfea50767a23fb8a004:21:40
@emilazy:matrix.orgemily you set services.resolved.fallbackDns and ensure UseDNS=no for networks 04:21:49
@hexa:lossy.networkhexa you could also just set services.resolved.enable = false and services.{unbound,kresd,pdns-recursor}.enable instead 04:22:32
@emilazy:matrix.orgemilysure04:22:39
@hexa:lossy.networkhexa they already set networking.dns.useLocalResolver 04:22:54
@hexa:lossy.networkhexa its just not helpful that resolved will fight useLocalResolver 04:23:15
@emilazy:matrix.orgemily but I suspect the dependencies on nss-resolve(8) and org.freedesktop.resolve1(5) will likely increase over time, that's all 04:23:20
@emilazy:matrix.orgemilypath of least resistance and most functionality is to let resolved be the API frontend for your underlying recursive resolver, for better or worse04:23:53
@hexa:lossy.networkhexahell no04:24:07
@hexa:lossy.networkhexaresolved does not perform at all04:24:13
@emilazy:matrix.orgemily part of the problem is that getaddrinfo(3)/gethostbyname(3) are useless APIs that are even more anaemic than other OS's native DNS APIs 04:24:58
@hexa:lossy.networkhexawe have systems at work that will put resolved at 100% cpu with queries and it will not keep up04:25:14
@emilazy:matrix.orgemilyso tons of applications have to reimplement their own DNS to begin with04:25:15
@emilazy:matrix.orgemilylovely04:25:25
@hexa:lossy.networkhexait's such a joke04:25:26
@emilazy:matrix.orgemilyare you sure that's not because of DNSSEC?04:25:29
@emilazy:matrix.orgemilyit tries to do DNSSEC validation OOTB04:25:34
@emilazy:matrix.orgemilyif you disable that and let your local resolver handle it I would be surprised if it has much overhead04:25:45
@hexa:lossy.networkhexayes, I'm sure that we didn't try to make it do DNSSEC related things 🙂 04:25:50
@emilazy:matrix.orgemilylike I said, OOTB04:25:57
@emilazy:matrix.orgemilyyou have to explicitly disable it04:26:01
@hexa:lossy.networkhexaagain04:26:04
@hexa:lossy.networkhexano offense04:26:07
@hexa:lossy.networkhexaI've been in the resolved dnssec issues years ago04:26:21
@hexa:lossy.networkhexaI'04:26:28
@hexa:lossy.networkhexa* I've killed dnssec support locally before it hit nixpkgs04:26:37
@hexa:lossy.networkhexabecause it wouldn't properly work and break resolution needlessly04:26:53
@emilazy:matrix.orgemilythe old DNSSEC issues are pretty depressing yeah04:27:15
@hexa:lossy.networkhexasystemd sometimes does to much and the developers are spread to thin04:27:19
@emilazy:matrix.orgemilyI think they have mostly been fixed by now but systemd upstream attitude to bug reports is depressing04:27:29

Show newer messages


Back to Room ListRoom Version: 6