<!DOCTYPE html> <html> <head> <link rel="Stylesheet" type="text/css" href="style.css"> <link rel="alternate" type="application/rss+xml" title="RSS" href="rss.xml"> <title>Blog Issue</title> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <meta name="viewport" content="width=device-width, initial-scale=1"> </head> <body> <hr /> <p> <a href="index.html">Index</a> <a href="home/tristan/Blog/blog/hello-world.html">Hello World</a> <hr /> </p> <p> <span id="-Date:"></span><strong id="Date:">Date:</strong> 2023/09/05 </p> <p> <span id="-Author:"></span><strong id="Author:">Author:</strong> Tristan Ancelet </p> <div id="Blog Issue"><h1 id="Blog Issue" class="header"><a href="#Blog Issue">Blog Issue</a></h1></div> <div id="Blog Issue-DNS"><h2 id="DNS" class="header"><a href="#Blog Issue-DNS">DNS</a></h2></div> <p> 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. </p> <p> 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 <span id="Blog Issue-DNS-DID"></span><strong id="DID">DID</strong> whitelist it but not perminately. So after a reboot it cleared the config and DNS traffic wasn't whitelisted it anymore. </p> <p> Here is the commands it did to whitelist DNS (running firewalld as a device side firewall) </p> <pre bash> firewall-cmd --perm --zone=public --add-service=dns firewall-cmd --reload </pre> <p> After checking that DNS was resolving with dig, I was able to visit my site with no more issues. </p> <pre bash> dig blog.tristanancelet.com </pre> </body> </html>