Automate the process of disabling systemd-resolved on dns servers
Context
systemd-resolved automatically binds to port 53 preventing dns servers from using it. This is an easy task to disable. However that task is being done manually for any dns hosts.
Proposed Changes
add the following task to dns_server role
stop and disable systemd-resolved
remove /etc/resolv.conf and create static file with correct nameserver to use
Verification Plan
verify /etc/resolv.conf is a static file
verify with ss -tupln that port 53 is only bound by the dsn container
### Summary
Automate the process of disabling systemd-resolved on dns servers
### Context
systemd-resolved automatically binds to port 53 preventing dns servers from using it. This is an easy task to disable. However that task is being done manually for any dns hosts.
### Proposed Changes
- [ ] add the following task to dns_server role
- [ ] stop and disable systemd-resolved
- [ ] remove /etc/resolv.conf and create static file with correct nameserver to use
### Verification Plan
- [ ] verify /etc/resolv.conf is a static file
- [ ] verify with `ss -tupln` that port 53 is only bound by the dsn container
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Automate the process of disabling systemd-resolved on dns servers
Context
systemd-resolved automatically binds to port 53 preventing dns servers from using it. This is an easy task to disable. However that task is being done manually for any dns hosts.
Proposed Changes
Verification Plan
ss -tuplnthat port 53 is only bound by the dsn container