<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Clockwork Notes</title><link>https://nazunalika.github.io/</link><description>Recent content on Clockwork Notes</description><generator>Hugo</generator><language>en-us</language><managingEditor>tucklesepk+blog@gmail.com (Louis Abel)</managingEditor><webMaster>tucklesepk+blog@gmail.com (Louis Abel)</webMaster><lastBuildDate>Sun, 10 May 2026 10:00:00 -0700</lastBuildDate><atom:link href="https://nazunalika.github.io/index.xml" rel="self" type="application/rss+xml"/><item><title>IPA: Using it for external DNS (the awkward way)</title><link>https://nazunalika.github.io/posts/2026-05-11-external-ipa-dns/</link><pubDate>Sun, 10 May 2026 10:00:00 -0700</pubDate><author>tucklesepk+blog@gmail.com (Louis Abel)</author><guid>https://nazunalika.github.io/posts/2026-05-11-external-ipa-dns/</guid><description>&lt;p&gt;I&amp;rsquo;ve been in the process of redoing my IPA domain at home. I decided that I
wanted a new domain while not changing ID&amp;rsquo;s, but also allowing me to control
some DNS domains that are external in the process.&lt;/p&gt;
&lt;p&gt;Traditionally, I have managed some domains with IPA while guaranteeing that some
are available externally and that if my IPA servers were down during
maintenance, bind on my AlmaLinux router would still serve DNS for my network.
This worked for the most part, actually, though I only had that one name server
that was known/usable. (You can imagine what happens when the one and only name
server for a domain stops responding to requests.)&lt;/p&gt;</description></item><item><title>Opinions</title><link>https://nazunalika.github.io/opinions/</link><pubDate>Thu, 23 Apr 2026 00:00:00 -0700</pubDate><author>tucklesepk+blog@gmail.com (Louis Abel)</author><guid>https://nazunalika.github.io/opinions/</guid><description>&lt;p&gt;This blog isn&amp;rsquo;t necessarily for opinions. However, I receive enough questions in
my email about what I think about &amp;ldquo;this&amp;rdquo; or &amp;ldquo;that.&amp;rdquo; To make it easier, I have
made this page to explain at some degree what I think about the various subject
matter I&amp;rsquo;ve been asked about.&lt;/p&gt;</description></item><item><title>Mikrotik: A new adventure in the networking world</title><link>https://nazunalika.github.io/posts/2024-05-19-mikrotik_adventure/</link><pubDate>Sun, 19 May 2024 14:20:00 -0700</pubDate><author>tucklesepk+blog@gmail.com (Louis Abel)</author><guid>https://nazunalika.github.io/posts/2024-05-19-mikrotik_adventure/</guid><description>&lt;p&gt;Recently, my HP ProCurve switch decided to die. It was one of those situations
where it didn&amp;rsquo;t make sense to try to repair it. However, this caused my entire
home network to go down, so I had to plug the things that I could directly into
my Linux router/lab box instead. Now normally, I&amp;rsquo;d be able to get another
ProCurve from my father, as he used to have access to pallets of them. However,
this is no longer the case, so I had to figure out what I wanted to do instead.&lt;/p&gt;</description></item><item><title>Resume</title><link>https://nazunalika.github.io/resume/</link><pubDate>Tue, 21 Mar 2023 17:25:35 -0700</pubDate><author>tucklesepk+blog@gmail.com (Louis Abel)</author><guid>https://nazunalika.github.io/resume/</guid><description>&lt;p&gt;Louis M. Abel&lt;/p&gt;
&lt;p&gt;Phoenix, AZ&lt;/p&gt;
&lt;h2 id="objective"&gt;Objective&lt;/h2&gt;
&lt;p&gt;To acquire a position in your Information Technology Department as an Administrator, Engineer, or Architect&lt;/p&gt;
&lt;h2 id="technical-skills"&gt;Technical Skills&lt;/h2&gt;
&lt;h2 id="notable-achievements"&gt;Notable Achievements&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Successful enterprise implementation for system access controls utilizing FreeIPA / Red Hat IdM with and without Active Directory trusts&lt;/li&gt;
&lt;li&gt;Successful implementation, maintenance, and enforcement of the CIS Benchmarks to ensure systems and applications are hardened beyond PCI compliance across both Linux, UNIX, Windows platforms as well as Middleware&lt;/li&gt;
&lt;li&gt;Successful enterprise implementation of both configuration and asset management via SaltStack, streamlining overall management of 4000+ on-prem and cloud Linux assets&lt;/li&gt;
&lt;li&gt;Successful migrations via PowerShell from vRealize 6 to 7.6 for clients that did not perform in-place upgrades&lt;/li&gt;
&lt;li&gt;Built and co-lead an open source team to create and release an Enterprise Linux distribution called &amp;ldquo;Rocky Linux&amp;rdquo; based on Red Hat Enterprise Linux and CentOS Stream&lt;/li&gt;
&lt;li&gt;Built and maintained many ansible roles and playbooks to maintain the Rocky Linux infrastructure&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="professional-experience"&gt;Professional Experience&lt;/h2&gt;
&lt;h2 id="open-source-contributions"&gt;Open Source Contributions&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;RPM maintainer for the Red Hat based Linux distributions based on Fedora Packaging Guidelines&lt;/li&gt;
&lt;li&gt;Maintain personal github repos for FreeIPA Identity Management, PCI compliance configurations for Red Hat Enterprise Linux systems, Discord Python plugins, and RPM build specs&lt;/li&gt;
&lt;li&gt;Collaborate and provide support for FreeIPA Identity Management and Fedora on mail list and IRC mediums&lt;/li&gt;
&lt;li&gt;Infrastructure, Identity Management, and Release Engineering for Rocky Linux&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="certifications"&gt;Certifications&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;RHCE - Red Hat Certified Engineer - April 14, 2025 - 120-155-718&lt;/li&gt;
&lt;li&gt;RHCSIM - Red Hat Certified Specialist in Identity Management - April 17, 2022 - 120-155-718&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Welcome</title><link>https://nazunalika.github.io/posts/welcome/</link><pubDate>Tue, 21 Mar 2023 17:17:36 -0700</pubDate><author>tucklesepk+blog@gmail.com (Louis Abel)</author><guid>https://nazunalika.github.io/posts/welcome/</guid><description>&lt;p&gt;More to come.&lt;/p&gt;</description></item></channel></rss>