2021-04-12 17:37:18 +01:00
|
|
|
{ config, lib, ... }:
|
2015-04-19 20:05:12 +01:00
|
|
|
|
|
|
|
with lib;
|
2016-06-26 21:58:04 +01:00
|
|
|
let
|
|
|
|
cfg = config.services.resolved;
|
2019-07-15 18:18:49 +01:00
|
|
|
|
|
|
|
dnsmasqResolve = config.services.dnsmasq.enable &&
|
|
|
|
config.services.dnsmasq.resolveLocalQueries;
|
|
|
|
|
2016-06-26 21:58:04 +01:00
|
|
|
in
|
2015-04-19 20:05:12 +01:00
|
|
|
{
|
|
|
|
|
|
|
|
options = {
|
|
|
|
|
|
|
|
services.resolved.enable = mkOption {
|
|
|
|
default = false;
|
|
|
|
type = types.bool;
|
|
|
|
description = ''
|
|
|
|
Whether to enable the systemd DNS resolver daemon.
|
|
|
|
'';
|
|
|
|
};
|
|
|
|
|
2016-06-26 21:58:04 +01:00
|
|
|
services.resolved.fallbackDns = mkOption {
|
|
|
|
default = [ ];
|
|
|
|
example = [ "8.8.8.8" "2001:4860:4860::8844" ];
|
|
|
|
type = types.listOf types.str;
|
|
|
|
description = ''
|
|
|
|
A list of IPv4 and IPv6 addresses to use as the fallback DNS servers.
|
|
|
|
If this option is empty, a compiled-in list of DNS servers is used instead.
|
|
|
|
'';
|
|
|
|
};
|
|
|
|
|
|
|
|
services.resolved.domains = mkOption {
|
|
|
|
default = config.networking.search;
|
2021-11-26 00:16:05 +00:00
|
|
|
defaultText = literalExpression "config.networking.search";
|
2016-06-26 21:58:04 +01:00
|
|
|
example = [ "example.com" ];
|
|
|
|
type = types.listOf types.str;
|
|
|
|
description = ''
|
2017-10-16 13:30:36 +01:00
|
|
|
A list of domains. These domains are used as search suffixes
|
|
|
|
when resolving single-label host names (domain names which
|
|
|
|
contain no dot), in order to qualify them into fully-qualified
|
|
|
|
domain names (FQDNs).
|
2019-05-13 08:15:17 +01:00
|
|
|
|
2017-10-16 13:30:36 +01:00
|
|
|
For compatibility reasons, if this setting is not specified,
|
|
|
|
the search domains listed in
|
|
|
|
<filename>/etc/resolv.conf</filename> are used instead, if
|
|
|
|
that file exists and any domains are configured in it.
|
2016-06-26 21:58:04 +01:00
|
|
|
'';
|
|
|
|
};
|
|
|
|
|
|
|
|
services.resolved.llmnr = mkOption {
|
|
|
|
default = "true";
|
|
|
|
example = "false";
|
|
|
|
type = types.enum [ "true" "resolve" "false" ];
|
|
|
|
description = ''
|
2017-10-16 13:30:36 +01:00
|
|
|
Controls Link-Local Multicast Name Resolution support
|
|
|
|
(RFC 4795) on the local host.
|
2019-05-13 08:15:17 +01:00
|
|
|
|
2017-10-16 13:30:36 +01:00
|
|
|
If set to
|
2019-05-13 08:15:17 +01:00
|
|
|
|
2017-10-16 13:30:36 +01:00
|
|
|
<variablelist>
|
|
|
|
<varlistentry>
|
|
|
|
<term><literal>"true"</literal></term>
|
|
|
|
<listitem><para>
|
|
|
|
Enables full LLMNR responder and resolver support.
|
|
|
|
</para></listitem>
|
|
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
|
|
|
<term><literal>"false"</literal></term>
|
|
|
|
<listitem><para>
|
|
|
|
Disables both.
|
|
|
|
</para></listitem>
|
|
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
|
|
|
<term><literal>"resolve"</literal></term>
|
|
|
|
<listitem><para>
|
|
|
|
Only resolution support is enabled, but responding is disabled.
|
|
|
|
</para></listitem>
|
|
|
|
</varlistentry>
|
|
|
|
</variablelist>
|
2016-06-26 21:58:04 +01:00
|
|
|
'';
|
|
|
|
};
|
|
|
|
|
|
|
|
services.resolved.dnssec = mkOption {
|
|
|
|
default = "allow-downgrade";
|
|
|
|
example = "true";
|
|
|
|
type = types.enum [ "true" "allow-downgrade" "false" ];
|
|
|
|
description = ''
|
2017-10-16 13:30:36 +01:00
|
|
|
If set to
|
|
|
|
<variablelist>
|
|
|
|
<varlistentry>
|
|
|
|
<term><literal>"true"</literal></term>
|
|
|
|
<listitem><para>
|
|
|
|
all DNS lookups are DNSSEC-validated locally (excluding
|
|
|
|
LLMNR and Multicast DNS). Note that this mode requires a
|
|
|
|
DNS server that supports DNSSEC. If the DNS server does
|
|
|
|
not properly support DNSSEC all validations will fail.
|
|
|
|
</para></listitem>
|
|
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
|
|
|
<term><literal>"allow-downgrade"</literal></term>
|
|
|
|
<listitem><para>
|
|
|
|
DNSSEC validation is attempted, but if the server does not
|
|
|
|
support DNSSEC properly, DNSSEC mode is automatically
|
|
|
|
disabled. Note that this mode makes DNSSEC validation
|
|
|
|
vulnerable to "downgrade" attacks, where an attacker might
|
|
|
|
be able to trigger a downgrade to non-DNSSEC mode by
|
|
|
|
synthesizing a DNS response that suggests DNSSEC was not
|
|
|
|
supported.
|
|
|
|
</para></listitem>
|
|
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
|
|
|
<term><literal>"false"</literal></term>
|
|
|
|
<listitem><para>
|
|
|
|
DNS lookups are not DNSSEC validated.
|
|
|
|
</para></listitem>
|
|
|
|
</varlistentry>
|
|
|
|
</variablelist>
|
2016-06-26 21:58:04 +01:00
|
|
|
'';
|
|
|
|
};
|
|
|
|
|
|
|
|
services.resolved.extraConfig = mkOption {
|
|
|
|
default = "";
|
|
|
|
type = types.lines;
|
|
|
|
description = ''
|
|
|
|
Extra config to append to resolved.conf.
|
|
|
|
'';
|
|
|
|
};
|
|
|
|
|
2015-04-19 20:05:12 +01:00
|
|
|
};
|
|
|
|
|
2016-06-26 21:58:04 +01:00
|
|
|
config = mkIf cfg.enable {
|
2015-04-19 20:05:12 +01:00
|
|
|
|
2019-07-15 18:18:49 +01:00
|
|
|
assertions = [
|
|
|
|
{ assertion = !config.networking.useHostResolvConf;
|
|
|
|
message = "Using host resolv.conf is not supported with systemd-resolved";
|
|
|
|
}
|
|
|
|
];
|
|
|
|
|
2020-11-05 12:47:19 +00:00
|
|
|
users.users.systemd-resolve.group = "systemd-resolve";
|
2019-11-24 21:46:10 +00:00
|
|
|
|
2020-05-05 12:41:12 +01:00
|
|
|
# add resolve to nss hosts database if enabled and nscd enabled
|
|
|
|
# system.nssModules is configured in nixos/modules/system/boot/systemd.nix
|
nixos/systemd: fix NSS database ordering
- The order of NSS (host) modules has been brought in line with upstream
recommendations:
- The `myhostname` module is placed before the `resolve` (optional) and `dns`
entries, but after `file` (to allow overriding via `/etc/hosts` /
`networking.extraHosts`, and prevent ISPs with catchall-DNS resolvers from
hijacking `.localhost` domains)
- The `mymachines` module, which provides hostname resolution for local
containers (registered with `systemd-machined`) is placed to the front, to
make sure its mappings are preferred over other resolvers.
- If systemd-networkd is enabled, the `resolve` module is placed before
`files` and `myhostname`, as it provides the same logic internally, with
caching.
- The `mdns(_minimal)` module has been updated to the new priorities.
If you use your own NSS host modules, make sure to update your priorities
according to these rules:
- NSS modules which should be queried before `resolved` DNS resolution should
use mkBefore.
- NSS modules which should be queried after `resolved`, `files` and
`myhostname`, but before `dns` should use the default priority
- NSS modules which should come after `dns` should use mkAfter.
2021-07-17 18:41:45 +01:00
|
|
|
# added with order 501 to allow modules to go before with mkBefore
|
|
|
|
system.nssDatabases.hosts = (mkOrder 501 ["resolve [!UNAVAIL=return]"]);
|
2020-05-05 12:41:12 +01:00
|
|
|
|
2017-01-26 00:52:38 +00:00
|
|
|
systemd.additionalUpstreamSystemUnits = [
|
2018-02-11 22:43:24 +00:00
|
|
|
"systemd-resolved.service"
|
2017-01-26 00:52:38 +00:00
|
|
|
];
|
2015-04-19 20:11:14 +01:00
|
|
|
|
2015-04-19 20:05:12 +01:00
|
|
|
systemd.services.systemd-resolved = {
|
|
|
|
wantedBy = [ "multi-user.target" ];
|
2020-05-08 13:15:41 +01:00
|
|
|
aliases = [ "dbus-org.freedesktop.resolve1.service" ];
|
2015-04-19 20:05:12 +01:00
|
|
|
restartTriggers = [ config.environment.etc."systemd/resolved.conf".source ];
|
|
|
|
};
|
|
|
|
|
2019-07-15 18:18:49 +01:00
|
|
|
environment.etc = {
|
|
|
|
"systemd/resolved.conf".text = ''
|
|
|
|
[Resolve]
|
|
|
|
${optionalString (config.networking.nameservers != [])
|
|
|
|
"DNS=${concatStringsSep " " config.networking.nameservers}"}
|
|
|
|
${optionalString (cfg.fallbackDns != [])
|
|
|
|
"FallbackDNS=${concatStringsSep " " cfg.fallbackDns}"}
|
|
|
|
${optionalString (cfg.domains != [])
|
|
|
|
"Domains=${concatStringsSep " " cfg.domains}"}
|
|
|
|
LLMNR=${cfg.llmnr}
|
|
|
|
DNSSEC=${cfg.dnssec}
|
|
|
|
${config.services.resolved.extraConfig}
|
|
|
|
'';
|
|
|
|
|
|
|
|
# symlink the dynamic stub resolver of resolv.conf as recommended by upstream:
|
|
|
|
# https://www.freedesktop.org/software/systemd/man/systemd-resolved.html#/etc/resolv.conf
|
|
|
|
"resolv.conf".source = "/run/systemd/resolve/stub-resolv.conf";
|
|
|
|
} // optionalAttrs dnsmasqResolve {
|
|
|
|
"dnsmasq-resolv.conf".source = "/run/systemd/resolve/resolv.conf";
|
|
|
|
};
|
2015-04-19 20:05:12 +01:00
|
|
|
|
2018-06-29 18:41:46 +01:00
|
|
|
# If networkmanager is enabled, ask it to interface with resolved.
|
|
|
|
networking.networkmanager.dns = "systemd-resolved";
|
2019-07-15 18:18:49 +01:00
|
|
|
|
2015-04-19 20:05:12 +01:00
|
|
|
};
|
|
|
|
|
|
|
|
}
|