Description of problem:
On Fedora 34, /etc/resolv.conf was a symbolic link after kickstart installation.
On Fedora 35, /etc/resolv.conf is a file created by NetworkManager.

On Fedora 34, systemd postinstall script creates the symbolic link of /etc/resolv.conf.

On Fedora 35, there is a new package systemd-resolved which contains the part of the postinstall script from systemd on Fedora 34 that creates the symbolic link of /etc/resolv.conf.

But the link is not created. It seams to me that a precondition is not true.

################################################################
if test -d /run/systemd/system/ &&
   systemctl -q is-enabled systemd-resolved.service &>/dev/null &&
   ! mountpoint /etc/resolv.conf &>/dev/null &&
   ! systemd-analyze cat-config systemd/resolved.conf 2>/dev/null | \
        grep -qE '^DNSStubListener\s*=\s*([nN][oO]?|[fF]|[fF][aA][lL][sS][eE]|0|[oO][fF][fF])$'; then
  ln -fsv ../run/systemd/resolve/stub-resolv.conf /etc/resolv.conf
fi
################################################################

On Fedora 34 I see in /var/log/anaconda/journal.log that service systemd-resolved was started and is running (I also did "ps -ef" in my kickstart %post section).

On Fedora 35, I found no running systemd-resolved during kickstart installation.

May it be that because of the split of package systemd in to systemd and systemd-resolved the order of installation is important? Script postinstall of systemd runs "systemctl preset-all". Script postinstall of systemd-resolved checks if service systemd-resolved is enabled. In the logs in /var/log/anaconda/journal.log I see that scriptlet of systemd-resolved is running before scriptlet of systemd.

May it be that service systemd-resolved is not enabled at the time when the scriptlet is running and so /etc/resolv.conf is not created as a symbolic link?

Because /etc/resolv.conf is not a symbolic link, NetworkManager creates the file as normal file and fills it with "search" and "nameserver" entries.


################################################################
Nov 07 13:44:21 anaconda[1964]: anaconda: modules.payloads.payload.dnf.transaction_progress: Installed: systemd-resolved-249.6-2.fc35.x86_64 1636036514 59e7de1798b271c53e617ff879204f27407ff97d5dd982d417bb8ef7479c6b3a
Nov 07 13:44:21 anaconda[1964]: anaconda: modules.payloads.payload.dnf.transaction_progress: Configuring (running scriptlet for): systemd-resolved-249.6-2.fc35.x86_64 1636036514 59e7de1798b271c53e617ff879204f27407ff97d5dd982d417bb8ef7479c6b3a
Nov 07 13:44:21 anaconda[1964]: anaconda: modules.payloads.payload.dnf.transaction_progress: Installed: systemd-249.6-2.fc35.x86_64 1636036514 c653f16fec9c819884ef931927da2a7ef3018c6e288eb40a3f9e93eaf536bdc5
Nov 07 13:44:23 anaconda[2627]: dnf: warning: group systemd-journal does not exist - using root
Nov 07 13:44:23 anaconda[1964]: anaconda: modules.payloads.payload.dnf.transaction_progress: Configuring (running scriptlet for): systemd-249.6-2.fc35.x86_64 1636036514 c653f16fec9c819884ef931927da2a7ef3018c6e288eb40a3f9e93eaf536bdc5
Nov 07 13:44:23  anaconda[2627]: dnf: Creating group input with gid 104.
                                                                  Creating group kvm with gid 36.
                                                                  Creating group render with gid 105.
                                                                  Creating group sgx with gid 106.
                                                                  Creating group systemd-journal with gid 190.
                                                                  Creating group systemd-network with gid 192.
                                                                  Creating user systemd-network (systemd Network Management) with uid 192 and gid 192.
                                                                  Creating group systemd-oom with gid 999.
                                                                  Creating user systemd-oom (systemd Userspace OOM Killer) with uid 999 and gid 999.
                                                                  Creating group systemd-resolve with gid 193.
                                                                  Creating user systemd-resolve (systemd Resolver) with uid 193 and gid 193.
                                                                  Creating group systemd-timesync with gid 998.
                                                                  Creating user systemd-timesync (systemd Time Synchronization) with uid 998 and gid 998.
                                                                  Creating group systemd-coredump with gid 997.
                                                                  Creating user systemd-coredump (systemd Core Dumper) with uid 997 and gid 997.
################################################################


Version-Release number of selected component (if applicable):
Fedora 35 Kickstart
systemd-resolved-249.6-2.fc35.x86_64


How reproducible:
Always

Steps to Reproduce:
1. Install Fedora 35 using kickstart.


Actual results:
/etc/resolv.conf is a normal file.

Expected results:
/etc/resolv.conf should be a symbolic link to the stub.


Additional info:
Bugzilla offers no component "systemd-resolved", so I choosed "systemd".