curben
/
blog
mirror of https://gitlab.com/curben/blog
1
0
Fork 0
Code Issues Releases Wiki Activity

post(log4shell): service unit needs to be unmasked 

before starting it
This commit is contained in:
Ming Di Leom 2021-12-17 09:30:58 +00:00
parent 6921550557
commit 13cb4353a2
No known key found for this signature in database
GPG Key ID: 32D3E28E96A695E8
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
source/_posts/log4shell-log4j-unbound-dns.md
View File

@ -108,9 +108,10 @@ sudo -e /etc/hosts
The last step before we start the service is to configure the firewall to allow inbound DNS traffic. I recommend not to allow all IP (0.0.0.0, ::0), otherwise you'll get unwanted traffic. In EC2, that means the attached security group. The last step before we start the service is to configure the firewall to allow inbound DNS traffic. I recommend not to allow all IP (0.0.0.0, ::0), otherwise you'll get unwanted traffic. In EC2, that means the attached security group.
After we configure the firewall, we can proceed to start Unbound. After we configure the firewall, we can proceed to unmask and start the DNS server.
``` ```
systemctl unmask unbound
systemctl enable --now unbound systemctl enable --now unbound
``` ```