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:26:52 -05:00
parent 146e7f28c4
commit 1e89fc1f64
2 changed files with 10 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
Site/blog-issue.html
View File

@ -36,28 +36,22 @@ 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)
```bash
</p> </p>
<ol> <ol>
<li> <li>
Adding the DNS service to the public zone and reloading firewalld to make sure the config change takes Adding the DNS service to the public zone and reloading firewalld to make sure the config change takes
</ol>
<p>
firewall-cmd --perm --zone=public --add-service=dns firewall-cmd --perm --zone=public --add-service=dns
firewall-cmd --reload firewall-cmd --reload
```
</p> </ol>
<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>
<p>
```bash
dig blog.tristanancelet.com dig blog.tristanancelet.com
``` </blockquote>
</p>
</body> </body>
</html> </html>

5
blog/blog-issue.wiki
View File

@ -16,16 +16,13 @@ Looks like my master DNS server was down for the last 3 days (didn't know until
I had a backup DNS server as well, but after looking into the VM (that was still running), it turns out that I never whitelisted the DNS port (53/udp) on it. So it's entire life has been failure (as it's been the backup for several months). My thought is that I *DID* whitelist it but not perminately. So after a reboot it cleared the config and DNS traffic wasn't whitelisted it anymore. I had a backup DNS server as well, but after looking into the VM (that was still running), it turns out that I never whitelisted the DNS port (53/udp) on it. So it's entire life has been failure (as it's been the backup for several months). My thought is that I *DID* whitelist it but not perminately. So after a reboot it cleared the config and DNS traffic wasn't whitelisted it anymore.
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
# Adding the DNS service to the public zone and reloading firewalld to make sure the config change takes # 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 --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
```