From d663bb0af2c20e3e9ca82a07e182fd64fc7715a4 Mon Sep 17 00:00:00 2001 From: Tristan Ancelet Date: Tue, 5 Sep 2023 21:31:11 -0500 Subject: [PATCH] Added new post --- Site/blog-issue.html | 19 ++++++++++--------- blog/blog-issue.wiki | 4 ++++ 2 files changed, 14 insertions(+), 9 deletions(-) diff --git a/Site/blog-issue.html b/Site/blog-issue.html index 72d5369..3cd8a47 100644 --- a/Site/blog-issue.html +++ b/Site/blog-issue.html @@ -37,19 +37,20 @@ 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)

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

-
-dig blog.tristanancelet.com -
+ +
+    dig blog.tristanancelet.com
+
diff --git a/blog/blog-issue.wiki b/blog/blog-issue.wiki index 992a152..87a250a 100644 --- a/blog/blog-issue.wiki +++ b/blog/blog-issue.wiki @@ -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) +{{{bash 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 +}}}