<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Cloudflare on Pieter Viljoen's Blog</title><link>https://blog.insanegenius.com/tag/cloudflare/</link><description>Recent content in Cloudflare on Pieter Viljoen's Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 29 May 2024 18:45:00 +0000</lastBuildDate><atom:link href="https://blog.insanegenius.com/tag/cloudflare/feed.xml" rel="self" type="application/rss+xml"/><item><title>Yet Another Cloudflare Traefik Let's Encrypt Guide</title><link>https://blog.insanegenius.com/2024/05/29/yet-another-cloudflare-traefik-lets-encrypt-guide/</link><pubDate>Wed, 29 May 2024 18:45:00 +0000</pubDate><guid isPermaLink="false">https://blog.insanegenius.com/2024/05/29/yet-another-cloudflare-traefik-lets-encrypt-guide/</guid><description>&lt;p&gt;There are many good guides on the internet on how to use and configure &lt;a href="https://www.cloudflare.com/products/tunnel/"&gt;Cloudflare Tunnels&lt;/a&gt;, &lt;a href="https://traefik.io/"&gt;Traefik&lt;/a&gt;, and &lt;a href="https://letsencrypt.org/"&gt;Let&amp;rsquo;s Encrypt&lt;/a&gt;, using &lt;a href="https://en.wikipedia.org/wiki/Wildcard_certificate"&gt;wildcard certificates&lt;/a&gt;, and &lt;a href="https://www.cloudflare.com/zero-trust/products/access/"&gt;Cloudflare Access&lt;/a&gt;, for authenticated home lab network access.&lt;/p&gt;
&lt;p&gt;This is yet another such guide, but using a single wildcard subdomain for remote homelab access. An advantage of using a wildcard subdomain is that the Cloudflare DNS and Tunnel and Access configuration only needs to be done once, and thereafter all access changes can be controlled through local homelab Traefik configuration. Another advantage is that services being exposed are not directly inferable by looking at DNS record names.&lt;/p&gt;</description></item><item><title>eNom Datacenter Move Borks DNS</title><link>https://blog.insanegenius.com/2022/01/17/enom-datacenter-move-borks-dns/</link><pubDate>Mon, 17 Jan 2022 19:52:26 +0000</pubDate><guid isPermaLink="false">https://blog.insanegenius.com/2022/01/17/enom-datacenter-move-borks-dns/</guid><description>&lt;p&gt;&lt;a href="https://www.enom.com/"&gt;eNom&lt;/a&gt; really &lt;a href="https://enomstatus.com/"&gt;borked&lt;/a&gt; their datacenter move resulting in two days and counting of no DNS.&lt;/p&gt;
&lt;p&gt;I first noticed the issue Saturday (15 Jan 2022) night when my inbox remained clean for several hours, yes, I am one of those people that like to keep email organized and the inbox clean. A bit of head scratching and googling led me to a reddit &lt;a href="https://www.reddit.com/r/sysadmin/comments/s4ucsk/enom_dns_down_anything_on_nameservicescom_etc/"&gt;post&lt;/a&gt; laying blame on the &lt;a href="https://enomstatus.com/incidents/3k436lhwz878"&gt;Enom Data Center Migration&lt;/a&gt; &lt;a href="https://twitter.com/enomsupport/status/1483062015862054915"&gt;gone wrong&lt;/a&gt;.&lt;/p&gt;
&lt;figure class="gallery gallery-cols-1"&gt;&lt;figure&gt;
&lt;img loading="lazy" src="https://blog.insanegenius.com/media/2022/01/2022-01-17-1.png?w=959"/&gt;
&lt;/figure&gt;
&lt;figure&gt;
&lt;img loading="lazy" src="https://blog.insanegenius.com/media/2022/01/2022-01-17-2.png?w=958"/&gt;
&lt;/figure&gt;
&lt;figure&gt;
&lt;img loading="lazy" src="https://blog.insanegenius.com/media/2022/01/2022-01-17-3.png?w=958"/&gt;
&lt;/figure&gt;
&lt;/figure&gt;
&lt;p&gt;I registered my first domain in 2000 over a dialup modem. Over time I&amp;rsquo;ve registered several more domains with several registrars (based on regional or TLD requirements of the day). In 2006 I consolidated all my registrations with eNom, in 2011 eNom transferred my account to BulkRegister, and in 2020 BulkRegister transferred my account to &lt;a href="https://www.hover.com/"&gt;Hover&lt;/a&gt;. So, today I am a Hover customer, and Hover is an eNom reseller, using eNom DNS services.&lt;/p&gt;</description></item></channel></rss>