Added new post
This commit is contained in:
parent
1e89fc1f64
commit
0d5881d1dc
@ -37,14 +37,10 @@ I had a backup DNS server as well, but after looking into the VM (that was still
|
||||
<p>
|
||||
Here is the commands it did to whitelist DNS (running firewalld as a device side firewall)
|
||||
</p>
|
||||
|
||||
<ol>
|
||||
<li>
|
||||
Adding the DNS service to the public zone and reloading firewalld to make sure the config change takes
|
||||
firewall-cmd --perm --zone=public --add-service=dns
|
||||
firewall-cmd --reload
|
||||
|
||||
</ol>
|
||||
<blockquote>
|
||||
firewall-cmd --perm --zone=public --add-service=dns
|
||||
firewall-cmd --reload
|
||||
</blockquote>
|
||||
|
||||
<p>
|
||||
After checking that DNS was resolving with dig, I was able to visit my site with no more issues.
|
||||
|
@ -17,7 +17,6 @@ I had a backup DNS server as well, but after looking into the VM (that was still
|
||||
|
||||
Here is the commands it did to whitelist DNS (running firewalld as a device side firewall)
|
||||
|
||||
# Adding the DNS service to the public zone and reloading firewalld to make sure the config change takes
|
||||
firewall-cmd --perm --zone=public --add-service=dns
|
||||
firewall-cmd --reload
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user