clement/personal-website
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Move indexes backwards by 1

Browse Source
This commit is contained in:
clement
2020-06-08 19:10:45 +08:00
parent d4c86054f4
commit 761c2f0c5c
20 changed files with 173 additions and 173 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
blog/content-002
View File

@ -1,18 +1,22 @@
<header>
<h1>The Migration</h1>
<h1>Configuring Dynamic DNS Records</h1>
</header>
<p>I've been moving from a rented place to another place, so I've been busy with those affairs instead of getting productive with my hobbies. Long story short, there were massive issues with my move and I was terribly preoccupied. </p>
<p>After moving to the new place, I realized that my website kept going down every other day. This immediately struck my interest as my IP address kept changing. At first, I thought it was a trigger-happy housemate restarting the Internet connection every time the average ping deviated by a few milliseconds. After configuring my A records for like the third time, I felt it was time to investigate.</p>
<p>Many important events have since been announced, mainly the release of RHEL8 and Debian 10. With this, Debian Stretch is counting down to its final hours. In typical Debian fasion, Buster is rock solid and is still as lean as it can be. They even have legacy support for iptables. I am very impressed. I am hoping that a team will pick up extended support for Stretch. The release of RHEL8 has been very unfortunate. I have been planning to take the RHCSA exam but I am worried that the exam will be testing on RHEL8 instead. If you have not read the changes, RHEL8 has made a rather radical departure from RHEL7, just like how RHEL7 did with its predecessor too. The release of AppStreams, the deprecation of yum, nftables and the like. </p>
<p>After a couple times of Googling, it turns out that the ISP at this new place is a smaller ISP. This ISP rotates the IP address every couple of days. So how would the laborious process of identifying my IP address, and then updating my A records be inevitable? Turns out not.</p>
<p>Looks like I would have to postpone taking my exam in the mean time.</p>
<p>The solution was to use Dynamic DNS, which actively updates my A records with my registrar. To do so, I had to install ddclient on my Debian install. However, the available ddclient on Debian Stretch was rather out of date. Getting the newer version was a simple affair of adding Buster's Unstable repos, then enabling it to start during boot. But wait, isn't Debian Buster already in stable? Turns out I had already configured ddclient some time ago prior moving to this new place, a time where Buster was still brewing in Unstable. What a pleasant surprise when I fired up sources.list.d only to find that everything was already there. Thank you, past self. </p>
<p>This is a rather short post, because I just wanted to update right after configuring the web server to work with the router. Thanks for reading.</p>
<h2>If ddclient was already configured, why would I still have issues with a IP address?</h2>
<p> After a bit of sleuthing, it turns out that I had to enable Dynamic DNS with my registrar, Namecheap. I had to also change my A records to what Namecheap calls A+ Dynamic DNS Records. With my A+ Dynamic DNS Records ready and ddclient's configuration double checked, I hesitantly left my server to its own devices.</p>
<p>It has been almost two weeks since that day, and everything is working fine. No downtime, no more stressful hours worrying about my server as I was stranded at work. What a relief. Well that's all I have to write for this post. Thanks for reading.</p>
<hr>
<p><div class="navbar">
<div><a href="blog-001">Prev</a></div>
<div><a href="blog-003">Next</a></div>
<div><a href="blog-002">Prev</a></div>
<div><a href="blog-004">Next</a></div>
</div></p>