!tCyGickeVqkHsYjWnh:nixos.org

NixOS Networking

921 Members
Declaratively manage your switching, routing, wireless, tunneling and more.267 Servers

Load older messages


SenderMessageTime
16 Jun 2025
@hexa:lossy.networkhexaI wish we could do better, but I fear there is no clear way out03:49:29
@zhaofeng:zhaofeng.liZhaofeng Li

proper resolver

oof

03:50:57
@zhaofeng:zhaofeng.liZhaofeng LiI want to love systemd, but a lot of the non-init pieces are too half-baked. Went all in with the declarative networkd configs but kept running into paper cuts03:52:30
@hexa:lossy.networkhexaby proper resolver I mean a recursor03:53:05
@hexa:lossy.networkhexa* by proper resolver I mean a recursor as opposed to a stub03:53:11
@hexa:lossy.networkhexaone that can actually validate dnssec for dane03:53:22
@hexa:lossy.networkhexa* one that can actually validate dnssec, e.g. for dane03:53:26
@emilazy:matrix.orgemilyresolved can talk to your resolver04:20:31
@emilazy:matrix.orgemily(and provides services like mDNS on top)04:20:37
@hexa:lossy.networkhexanot interesting for my server04:20:58
@hexa:lossy.networkhexa* not interesting for my servers04:21:03
@emilazy:matrix.orgemilyit's pretty much the supported configuration for better or worse. like, it also provides the D-Bus resolved API etc. and works with the NSS stuff04:21:24
@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

Show newer messages


Back to Room ListRoom Version: 6