Skip to main content

The Great Domain Migration to NameCheap

 


As you may not know, but now know, Google Domains is being sold to Squarespace -- To the annoyed groans of many around the world, myself included.

 Word spread on Twitter (I will not call it X) on how Squarespace was often a costlier option for people. I don't remember exact numbers people had experience with, but it was more. 36$/yr sticks in my head, but check for yourself.

With a domain costing 12$ through Google, I thought above making the choice to transfer myself; and after perusing this Twitter thread, decided to go with Namecheap on a whim.

I didn't know there were so many choices to host domains, DNS options, email services. That would actually be a field of interest to own a business in. It has that old internet charm (robot text anyone?).

Now, this very site is hosted on Blogger, which is owned (and ignored) by Google, so it probably isn't being killed anytime soon (I hope). Google Domains was owned by, well, Google, so attaching the domain to the site was quite easy. 

I even had email forwarding.

I transferred to Namecheap with minimal issues, and that's where things get annoying. To be clear, Namecheap did nothing wrong, though, based upon Trustpilot reviews, I think our business begins and ends with simply owning my domain. 

Everyone was helpful and patient!

 I forgot about the rigamarole of putting in CNAME records, A records into a domain registrar to point things in the right direction -- and Blogger doesn't make it easy to find.

It should appear when you put in a domain name. But if you already have it there, what then? I changed the domain to a nonexistent one to get the CNAME records, but those were apparently not accurate.

  • When I used Google Search Console, it said I didn't own the domain -- it had passed into the whoisregistrar and the info was hidden, a setting on Namecheap. 
  • An email had escaped my notice to confirm the domain was mine, so that was easily solved.
  • A semi-new feature is browers automatically using https to connect you to websites that allow it. I had to (re?) allow this feature on Blogger, or secure connections couldn't visit.

 The Blogger help community is being kept alive by one good person over here, in my topic.

Am I sure I have everything pointed to the right places? Possibly. If not, we'll figure it out soon, won't we.

Labels:

Comments

Post a Comment

Popular posts from this blog

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an intruder, but it is a step. There are no devices associated with this new server; In an earlier lab (not shown), I attached them to 'H
Post a Comment
Read more

Create a Simple Network (Packet Tracer) + A Walkthrough

Again; I've done this, but now there's so many new things, I'm doing it again. The truly new portions were...everything on the right side of this diagram; The cloud needed a coax connector and a copper Ethernet connector. It's all easy to install, turn off the cloud (Weird), install the modules. Getting the Cable section of Connections was an unusual struggle - The other drop down menu had nothing within. It required going into the Ethernet options and setting the Provider Network to 'cable', which is the next step AFTER the drop-downs. The rest was typical DHCP and DNS setups, mainly on the Cisco server down there. The post is rather short - How about adding a video to it? Find out what A Record means - This site says 'Maps a name to an IP address', which is DNS. So it's another name for DNS? You can change them (presumably in a local context) to associate an IP address to another name.
Post a Comment
Read more

Securing Terraform and You Part 1 -- rego, Tfsec, and Terrascan

9/20: The open source version of Terraform is now  OpenTofu     Sometimes, I write articles even when things don't work. It's about showing a learning process.  Using IaC means consistency, and one thing you don't want to do is have 5 open S3 buckets on AWS that anyone on the internet can reach.  That's where tools such as Terrascan and Tfsec come in, where we can make our own policies and rules to be checked against our code before we init.  As this was contract work, I can't show you the exact code used, but I can tell you that this blog post by Cesar Rodriguez of Cloud Security Musings was quite helpful, as well as this one by Chris Ayers . The issue is using Rego; I found a cool VS Code Extension; Terrascan Rego Editor , as well as several courses on Styra Academy; Policy Authoring and Policy Essentials . The big issue was figuring out how to tell Terrascan to follow a certain policy; I made it, put it in a directory, and ran the program while in that directory
Post a Comment
Read more