ansible-roles/dns_resolver_conf
ansible-roles/dns_resolver_conf
4
0
Fork 0
Code Issues 3 Pull Requests Actions Packages Projects Releases Wiki Activity

Role needs to take full advantage ofsystemd-resolved if it is not being disabled #2

New Issue
Open
opened 2023-12-01 17:47:34 +00:00 by lanson · 0 comments
lanson commented 2023-12-01 17:47:34 +00:00
Owner
Copy Link

Right now, even if you keep systemd-resolved(resolvctl) running, the role will actually configure /etc/resolv.conf to bypass it.

It needs to use it (ie provision the correct config files in /run/systemd/resolve), if the service isn't marked to be disabled in the defaults, AND if the service actually exists.

Right now, even if you keep systemd-resolved(resolvctl) running, the role will actually configure /etc/resolv.conf to bypass it. It needs to use it (ie provision the correct config files in `/run/systemd/resolve`), if the service isn't marked to be disabled in the defaults, AND if the service actually exists.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: ansible-roles/dns_resolver_conf#2
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?