diff --git a/Site/blog-issue.html b/Site/blog-issue.html index 551dcf2..64bf136 100644 --- a/Site/blog-issue.html +++ b/Site/blog-issue.html @@ -36,28 +36,22 @@ 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) -```bash

+
  1. 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
-

-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 -``` -

+
diff --git a/blog/blog-issue.wiki b/blog/blog-issue.wiki index 3bcd177..f3f8797 100644 --- a/blog/blog-issue.wiki +++ b/blog/blog-issue.wiki @@ -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. 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 -``` + + # 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 -``` + dig blog.tristanancelet.com