diff options
| author | Majiir Paktu <majiir@nabaal.net> | 2023-10-02 17:36:08 -0400 |
|---|---|---|
| committer | Majiir Paktu <majiir@nabaal.net> | 2023-10-02 17:36:08 -0400 |
| commit | 0ba49949b087f0b358dafc118588f80dabcc885e (patch) | |
| tree | 98533e453fbab6266bf413cc88a9d88a58c7dce4 /pkgs/development/python-modules/rangehttpserver | |
| parent | b200dcc8b13cb67e867c83e26dbbbd08ad90bc9b (diff) | |
nixos/network-interfaces-systemd: don't set network-level domains
systemd.network(5) describes Domains= as a "list of domains which should
be resolved using the DNS servers on this link." This setting is read by
systemd-resolved.service, and it's used to configure both search domains
and DNS query routing.
Adding the search domains from `networking.search` is unnecessary
because these are already configured globally in `resolved.conf` through
the default value of `services.resolved.domains`.
Adding the system's `networking.domain` to each network is unexpected
and probably incorrect. A user may not expect that the domain is in
effect automatically added to the search domains even if not specified
in `networking.search`.
Both of these network-level assignments are problematic in cases where
the NixOS networkd module is not managing every interface on the system.
In that scenario, the managed interfaces will have Domains= set while
the others do not. That will cause systemd-resolved to route DNS queries
for the search domains and the system domain to only those managed
interfaces.
Diffstat (limited to 'pkgs/development/python-modules/rangehttpserver')
0 files changed, 0 insertions, 0 deletions
