This is a MAJOR development with Redhat NO LONGER giving public access to the base RHEL source code. Support My Work-----------------------------------------...
Potentially this means that Fedora and CentOS stream do not get timely updates implemented in RHEL.
Canonical must be throwing a party, and I bet SUSE is not hating it either
They see all the other stuff that gets packaged under the systemd name and assume it’s non-optional. While many distributions do, annoyingly, ship the auxiliary packages like resolved by default, they’re not required if you just want to use the init system, and honestly they kind of strike me as an attempt to supplement or replace some of the incumbent components of your average distro.
Systemd-resolved can suck my whole grundle, though.
i see you have not tried to configure and debug dynamic split dns setups that are very common in enterprise vpn world.
before systemd-resolved you had to use dnsmasq running on localhost with bunch of shell scripts to reconfigure it when vpn interfaces come and go for split horizon dns to work propperly.
now with systemd-resolved you can easily tell it what dns prefixes are handeled by what dns server and everything is nicely cleaned up after vpn goes down.
They see all the other stuff that gets packaged under the systemd name and assume it’s non-optional. While many distributions do, annoyingly, ship the auxiliary packages like resolved by default, they’re not required if you just want to use the init system, and honestly they kind of strike me as an attempt to supplement or replace some of the incumbent components of your average distro.
Systemd-resolved can suck my whole grundle, though.
@eltimablo @SmokeInFog @words_number @vegivamp @bigkahuna1986
“Systemd-resolved can suck my whole grundle, though.”
Actual lol, and I agree. I’ve kinda learned to live with it and to most keep it out of the way, but seriously what a pain.
i see you have not tried to configure and debug dynamic split dns setups that are very common in enterprise vpn world.
before systemd-resolved you had to use dnsmasq running on localhost with bunch of shell scripts to reconfigure it when vpn interfaces come and go for split horizon dns to work propperly.
now with systemd-resolved you can easily tell it what dns prefixes are handeled by what dns server and everything is nicely cleaned up after vpn goes down.