systemd-resolved stub resolver and /etc/resolv.conf symbolic link configuration

Red Hat Enterprise Linux utilizes systemd-resolved to manage network name resolution, providing a local DNS stub listener at 127.0.0.53. This architecture allows for per-interface DNS routing and integrated caching to optimize query latency.

Standard integration requires /etc/resolv.conf to be a symbolic link pointing to /run/systemd/resolve/stub-resolv.conf. However, uncertainty arises when specific application requirements demand a static resolver configuration that bypasses the local stub while still utilizing the systemd-resolved backend for other system services.

• What is the recommended configuration to maintain systemd-resolved for system-wide routing while providing a non-stubbed resolver file for specific legacy applications?
• How does the system handle conflicts if /etc/resolv.conf is converted to a regular file while the systemd-resolved service remains active?