<?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>Enom on Pieter Viljoen's Blog</title><link>https://blog.insanegenius.com/tag/enom/</link><description>Recent content in Enom on Pieter Viljoen's Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 17 Jan 2022 19:52:26 +0000</lastBuildDate><atom:link href="https://blog.insanegenius.com/tag/enom/feed.xml" rel="self" type="application/rss+xml"/><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><item><title>eNom Dynamic DNS Update Problems</title><link>https://blog.insanegenius.com/2018/06/30/enom-dynamic-dns-update-problems/</link><pubDate>Sat, 30 Jun 2018 16:57:07 +0000</pubDate><guid isPermaLink="false">https://blog.insanegenius.com/2018/06/30/enom-dynamic-dns-update-problems/</guid><description>&lt;p&gt;&lt;em&gt;Update: On 27 July 2018 eNom support notified me by email that the issue is resolved. I tested it, and all is back to normal with DNS-O-Matic.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Sometime between 12 May 2018 and 24 May 2018 the &lt;a href="https://help.enom.com/hc/en-us/articles/115002224432-Dynamic-DNS-FAQs"&gt;eNom dynamic DNS&lt;/a&gt; update mechanism stopped working.&lt;/p&gt;
&lt;p&gt;I use the very convenient &lt;a href="https://www.dnsomatic.com/"&gt;DNS-O-Matic&lt;/a&gt; dynamic DNS update service to update my OpenDNS account, and several host records at eNom, pointing them to my home IP address.&lt;/p&gt;</description></item></channel></rss>