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:24:29 -05:00
parent 60debb69a7
commit a1f66d8345
2 changed files with 37 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

31
blog/blog-issue.wiki Normal file
View File

@ -0,0 +1,31 @@
%title Blog Issue
---------------------------
[[index.wiki|Index]] [[/home/tristan/Blog/blog/hello-world.wiki|Hello World]]
---------------------------
*Date:* 2023/09/05
*Author:* Tristan Ancelet
= Blog Issue =
== DNS ==
Looks like my master DNS server was down for the last 3 days (didn't know until the teacher mentioned it). Had to end up taking a look at my provider and it looks like my master DNS server had crashed at some point. After restarting it I got everything started up and it seems to have come back up.
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)
```bash
# 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
```
After checking that DNS was resolving with dig, I was able to visit my site with no more issues.
```bash
dig blog.tristanancelet.com
```

10
blog/index.wiki
View File

@ -1,10 +1,12 @@
%title Blog Index
----
--------
[[about-me.wiki|About Me]]
----
--------
= Blog Posts =
--------------
## Blog Posts
-------------
[[blog-issue.wiki|Blog Issue (2023/09/05)]]
[[hello-world.wiki|Hello World (2023/09/02)]]