tristan/blog
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Added new post

Browse Source
This commit is contained in:
Tristan Ancelet 2023-09-05 21:31:11 -05:00
parent 804cdf676a
commit d663bb0af2
2 changed files with 14 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
Site/blog-issue.html
View File

@ -37,19 +37,20 @@ I had a backup DNS server as well, but after looking into the VM (that was still
<p> <p>
Here is the commands it did to whitelist DNS (running firewalld as a device side firewall) Here is the commands it did to whitelist DNS (running firewalld as a device side firewall)
</p> </p>
<blockquote>
<pre bash>
firewall-cmd --perm --zone=public --add-service=dns firewall-cmd --perm --zone=public --add-service=dns
</blockquote>
<blockquote>
firewall-cmd --reload firewall-cmd --reload
</blockquote> </pre>
<p> <p>
After checking that DNS was resolving with dig, I was able to visit my site with no more issues. After checking that DNS was resolving with dig, I was able to visit my site with no more issues.
</p> </p>
<blockquote>
<pre bash>
dig blog.tristanancelet.com dig blog.tristanancelet.com
</blockquote> </pre>
</body> </body>
</html> </html>

4
blog/blog-issue.wiki
View File

@ -17,12 +17,16 @@ 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) Here is the commands it did to whitelist DNS (running firewalld as a device side firewall)
{{{bash
firewall-cmd --perm --zone=public --add-service=dns firewall-cmd --perm --zone=public --add-service=dns
firewall-cmd --reload firewall-cmd --reload
}}}
After checking that DNS was resolving with dig, I was able to visit my site with no more issues. After checking that DNS was resolving with dig, I was able to visit my site with no more issues.
{{{bash
dig blog.tristanancelet.com dig blog.tristanancelet.com
}}}