···
567
+
The order of NSS (host) modules has been brought in line with
568
+
upstream recommendations:
570
+
<itemizedlist spacing="compact">
573
+
The <literal>myhostname</literal> module is placed before
574
+
the <literal>resolve</literal> (optional) and
575
+
<literal>dns</literal> entries, but after
576
+
<literal>file</literal> (to allow overriding via
577
+
<literal>/etc/hosts</literal> /
578
+
<literal>networking.extraHosts</literal>, and prevent ISPs
579
+
with catchall-DNS resolvers from hijacking
580
+
<literal>.localhost</literal> domains)
585
+
The <literal>mymachines</literal> module, which provides
586
+
hostname resolution for local containers (registered with
587
+
<literal>systemd-machined</literal>) is placed to the
588
+
front, to make sure its mappings are preferred over other
594
+
If systemd-networkd is enabled, the
595
+
<literal>resolve</literal> module is placed before
596
+
<literal>files</literal> and
597
+
<literal>myhostname</literal>, as it provides the same
598
+
logic internally, with caching.
603
+
The <literal>mdns(_minimal)</literal> module has been
604
+
updated to the new priorities.
609
+
If you use your own NSS host modules, make sure to update your
610
+
priorities according to these rules:
612
+
<itemizedlist spacing="compact">
615
+
NSS modules which should be queried before
616
+
<literal>resolved</literal> DNS resolution should use
622
+
NSS modules which should be queried after
623
+
<literal>resolved</literal>, <literal>files</literal> and
624
+
<literal>myhostname</literal>, but before
625
+
<literal>dns</literal> should use the default priority
630
+
NSS modules which should come after <literal>dns</literal>
631
+
should use mkAfter.