Bug 1815605
| Summary: | resolvctl does not update /etc/resolv.conf | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dimitri Papadopoulos <dimitri.papadopoulos> |
| Component: | systemd | Assignee: | systemd-maint |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 31 | CC: | lnykryn, msekleta, s, systemd-maint, zbyszek |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | systemd-245.6-2.fc32 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-06-05 02:29:26 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Dimitri Papadopoulos
2020-03-20 17:12:53 UTC
Your /etc/resolv.conf is managed by NetworkManager. And resolvconf only talks to systemd-resolved. If you do 'resolvectl status enp0s3', do the new nameservers show up in there? (I read the man page now, and it doesn't explain this very well.) I do understand there are two independent subsystems involved in name resolution, not counting NetworkManager which operates on top: * glibc+NSS * systemd-resolved It just seemed "obvious" to me that the tools used to modify the settings of either subsystem would be interoperable and would modify both subsystems. That seemed all the more "obvious" for the "resolveconf" alias of "resolvectl". I understand now this is not obvious at all and the that these two subsystems remain rather independent. And yes, systemd-resolved is updated by resolvconf and this shows when running 'resolvectl status enp0s3' later on. It would be great if the documentation could be improved. On the other hand I have discovered that in the long term (Fedora 33) glibc will switch from NSS to systemd-resolved by default, so the two subsystems would be "merged" (by default): https://fedoraproject.org/wiki/Changes/systemd-resolved Perhaps it's not worth spending too much energy temporarily fixing docs that will need to be modified in less than 12 months from now anyway. FEDORA-2020-dd43dd05b1 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-dd43dd05b1 FEDORA-2020-dd43dd05b1 has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-dd43dd05b1` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-dd43dd05b1 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-dd43dd05b1 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-dd43dd05b1 FEDORA-2020-dd43dd05b1 has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-dd43dd05b1` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-dd43dd05b1 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-dd43dd05b1 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report. |