Bug 1955888
Summary: | systemd-resolved takes over port 53 preventing dnsmasq to start | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Adam Pribyl <covex> |
Component: | systemd | Assignee: | systemd-maint |
Status: | CLOSED CANTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 33 | CC: | fedoraproject, filbranden, flepied, kasong, lnykryn, msekleta, ssahani, s, systemd-maint, yuwatana, zbyszek |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-05-15 10:33:32 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
Adam Pribyl
2021-05-01 09:53:53 UTC
You'll need to disable the stub listener. Please create /etc/systemd/resolved.conf.d/stub-listener.conf: [Resolve] DNSStubListener=no I'll close the bug though: it's just something that will need to be handled through an explicit configuration from the admin. This is however a problem if you update a remote system, and whole network remains without DHCP due to that. I'd propose that this should be handled by package maintainer at last. Either the systemd-resolved should be started after a dnsmasq or similar services, or it should not be configured for start if there is another resolver already configured. There is an unlimited number of other resolvers that may be running. There is no mechanism to ask "will there be some precess listening on port 53?". I added a section in the Change page to mention this more: https://fedoraproject.org/wiki/Changes/systemd-resolved#Local_stub_resolver_on_port_53 |