···78---
910-**Describe the bug**
11A clear and concise description of what the bug is.
1213-**To Reproduce**
14Steps to reproduce the behavior:
151. ...
162. ...
173. ...
1819-**Expected behavior**
20A clear and concise description of what you expected to happen.
2122-**Screenshots**
23If applicable, add screenshots to help explain your problem.
2425-**Additional context**
26Add any other context about the problem here.
2728-**Notify maintainers**
29<!--
30Please @ people who are in the `meta.maintainers` list of the offending package or module.
31If in doubt, check `git blame` for whoever last touched something.
32-->
3334-**Metadata**
35Please run `nix-shell -p nix-info --run "nix-info -m"` and paste the result.
000003637Maintainer information:
38```yaml
···78---
910+### Describe the bug
11A clear and concise description of what the bug is.
1213+### Steps To Reproduce
14Steps to reproduce the behavior:
151. ...
162. ...
173. ...
1819+### Expected behavior
20A clear and concise description of what you expected to happen.
2122+### Screenshots
23If applicable, add screenshots to help explain your problem.
2425+### Additional context
26Add any other context about the problem here.
2728+### Notify maintainers
29<!--
30Please @ people who are in the `meta.maintainers` list of the offending package or module.
31If in doubt, check `git blame` for whoever last touched something.
32-->
3334+### Metadata
35Please run `nix-shell -p nix-info --run "nix-info -m"` and paste the result.
36+37+```console
38+[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
39+output here
40+```
4142Maintainer information:
43```yaml
···617 be removed in 22.05.
618 </para>
619 </listitem>
00000000000000000000000000000000000000000000000000000000000000000000000620 </itemizedlist>
621 </section>
622</section>
···617 be removed in 22.05.
618 </para>
619 </listitem>
620+ <listitem>
621+ <para>
622+ The order of NSS (host) modules has been brought in line with
623+ upstream recommendations:
624+ </para>
625+ <itemizedlist spacing="compact">
626+ <listitem>
627+ <para>
628+ The <literal>myhostname</literal> module is placed before
629+ the <literal>resolve</literal> (optional) and
630+ <literal>dns</literal> entries, but after
631+ <literal>file</literal> (to allow overriding via
632+ <literal>/etc/hosts</literal> /
633+ <literal>networking.extraHosts</literal>, and prevent ISPs
634+ with catchall-DNS resolvers from hijacking
635+ <literal>.localhost</literal> domains)
636+ </para>
637+ </listitem>
638+ <listitem>
639+ <para>
640+ The <literal>mymachines</literal> module, which provides
641+ hostname resolution for local containers (registered with
642+ <literal>systemd-machined</literal>) is placed to the
643+ front, to make sure its mappings are preferred over other
644+ resolvers.
645+ </para>
646+ </listitem>
647+ <listitem>
648+ <para>
649+ If systemd-networkd is enabled, the
650+ <literal>resolve</literal> module is placed before
651+ <literal>files</literal> and
652+ <literal>myhostname</literal>, as it provides the same
653+ logic internally, with caching.
654+ </para>
655+ </listitem>
656+ <listitem>
657+ <para>
658+ The <literal>mdns(_minimal)</literal> module has been
659+ updated to the new priorities.
660+ </para>
661+ </listitem>
662+ </itemizedlist>
663+ <para>
664+ If you use your own NSS host modules, make sure to update your
665+ priorities according to these rules:
666+ </para>
667+ <itemizedlist spacing="compact">
668+ <listitem>
669+ <para>
670+ NSS modules which should be queried before
671+ <literal>resolved</literal> DNS resolution should use
672+ mkBefore.
673+ </para>
674+ </listitem>
675+ <listitem>
676+ <para>
677+ NSS modules which should be queried after
678+ <literal>resolved</literal>, <literal>files</literal> and
679+ <literal>myhostname</literal>, but before
680+ <literal>dns</literal> should use the default priority
681+ </para>
682+ </listitem>
683+ <listitem>
684+ <para>
685+ NSS modules which should come after <literal>dns</literal>
686+ should use mkAfter.
687+ </para>
688+ </listitem>
689+ </itemizedlist>
690+ </listitem>
691 </itemizedlist>
692 </section>
693</section>
+24
nixos/doc/manual/release-notes/rl-2111.section.md
···155- The wordpress module provides a new interface which allows to use different webservers with the new option [`services.wordpress.webserver`](options.html#opt-services.wordpress.webserver). Currently `httpd` and `nginx` are supported. The definitions of wordpress sites should now be set in [`services.wordpress.sites`](options.html#opt-services.wordpress.sites).
156157 Sites definitions that use the old interface are automatically migrated in the new option. This backward compatibility will be removed in 22.05.
000000000000000000000000
···155- The wordpress module provides a new interface which allows to use different webservers with the new option [`services.wordpress.webserver`](options.html#opt-services.wordpress.webserver). Currently `httpd` and `nginx` are supported. The definitions of wordpress sites should now be set in [`services.wordpress.sites`](options.html#opt-services.wordpress.sites).
156157 Sites definitions that use the old interface are automatically migrated in the new option. This backward compatibility will be removed in 22.05.
158+159+- The order of NSS (host) modules has been brought in line with upstream
160+ recommendations:
161+162+ - The `myhostname` module is placed before the `resolve` (optional) and `dns`
163+ entries, but after `file` (to allow overriding via `/etc/hosts` /
164+ `networking.extraHosts`, and prevent ISPs with catchall-DNS resolvers from
165+ hijacking `.localhost` domains)
166+ - The `mymachines` module, which provides hostname resolution for local
167+ containers (registered with `systemd-machined`) is placed to the front, to
168+ make sure its mappings are preferred over other resolvers.
169+ - If systemd-networkd is enabled, the `resolve` module is placed before
170+ `files` and `myhostname`, as it provides the same logic internally, with
171+ caching.
172+ - The `mdns(_minimal)` module has been updated to the new priorities.
173+174+ If you use your own NSS host modules, make sure to update your priorities
175+ according to these rules:
176+177+ - NSS modules which should be queried before `resolved` DNS resolution should
178+ use mkBefore.
179+ - NSS modules which should be queried after `resolved`, `files` and
180+ `myhostname`, but before `dns` should use the default priority
181+ - NSS modules which should come after `dns` should use mkAfter.
···9 hardware.sensor.iio = {
10 enable = mkOption {
11 description = ''
12- Enable this option to support IIO sensors.
1314 IIO sensors are used for orientation and ambient light
15 sensors on some mobile devices.
···9 hardware.sensor.iio = {
10 enable = mkOption {
11 description = ''
12+ Enable this option to support IIO sensors with iio-sensor-proxy.
1314 IIO sensors are used for orientation and ambient light
15 sensors on some mobile devices.
···140141 # add resolve to nss hosts database if enabled and nscd enabled
142 # system.nssModules is configured in nixos/modules/system/boot/systemd.nix
143- system.nssDatabases.hosts = optional config.services.nscd.enable "resolve [!UNAVAIL=return]";
0144145 systemd.additionalUpstreamSystemUnits = [
146 "systemd-resolved.service"
···140141 # add resolve to nss hosts database if enabled and nscd enabled
142 # system.nssModules is configured in nixos/modules/system/boot/systemd.nix
143+ # added with order 501 to allow modules to go before with mkBefore
144+ system.nssDatabases.hosts = (mkOrder 501 ["resolve [!UNAVAIL=return]"]);
145146 systemd.additionalUpstreamSystemUnits = [
147 "systemd-resolved.service"