What it was like to have Claude as my assistant

For years, my blog lived on WordPress at DreamHost, and DreamHost also held my domain registration. I was generally happy with it: DreamHost kept PHP and everything else up to date for me. Then a critical PHP issue came along, and even though DreamHost handled it, it made me realize I didn't want a website that depends on a web server and WordPress anymore. None of that was DreamHost's fault. So I finally decided to move everything: the domain registration to Namecheap, where I already had another domain, so it made sense to keep them in one place instead of paying for domain registration in two places, which keeps billing simple, and the blog to Squarespace, where I already had a free account through a work benefit and knew the setup well, so moving there was easy.

There was one rule I wasn't willing to bend. My email runs on Google Workspace with my own domain, and I really didn't want it down for long.

This time I didn't do it alone. I already had a Claude subscription, and I wanted to see how AI could help with something I don't do regularly. I'm comfortable with technical concepts, but I'm no networking or DNS expert. I did the whole move with Claude as a guide, over about two weeks of short evening sessions.

A quick bit of background, in plain words: registering a domain is like owning an address, and DNS is the directory that tells the internet where that address's website and email actually live. The nameservers are simply where that directory is kept. The registration and the directory can sit at different companies, and that turned out to matter a lot.

How I worked with Claude

I started by telling Claude three things: which domain was moving, that my DNS was hosted at DreamHost, and that every post and image should come over to Squarespace, with private posts staying private. Within a few minutes it had looked up my domain's public DNS records and written a step-by-step migration plan, split into phases, that I could edit and comment on.

The way we worked was simple. Claude never had my passwords and never logged in anywhere. I did every click myself. When something needed checking, Claude gave me a command to run on my own computer, and I pasted the output back. It then told me whether things matched, what to fix, and, just as important, when to wait and not touch anything.

Step 1: Move DNS before anything else

I knew what I wanted to end up with, and just as clearly, what must not happen along the way. There's a joke about AI: someone holds up a mushroom and asks an AI whether it's edible. The AI says yes, and fails to mention that it's also deadly. So I made sure to tell Claude both what I wanted to accomplish and what I couldn't afford to have go wrong. What I didn't know was how to get there. Claude's plan answered that. If I moved DNS to Namecheap first, while DreamHost was still the registrar, my email would never depend on the registrar transfer going smoothly.

So I copied every record from DreamHost into Namecheap by hand, with Claude translating between the two control panels, which label things differently and don't agree on what should be copied at all.

Once every record, especially the mail ones, answered correctly from Namecheap, I switched the nameservers at DreamHost. Email kept working the entire time.

Step 2: Take WordPress offline

With the blog already imported into Squarespace, I parked the old WordPress site at DreamHost, a little sooner than Claude suggested. It wanted me to wait a few hours for the nameserver change to spread, just in case. It turned out fine: parking only took the old site offline, and my email wasn't affected.

Step 3: Transfer the registration

The registrar transfer itself was the most boring part: unlock the domain, get the authorization code, start the transfer at Namecheap, and wait about five days. When it finished, a quick check confirmed all the mail records had come along.

Step 4: Connect Squarespace without breaking email

This is where I made my biggest mistake of the whole move, and I want to be honest about it, because how I recovered is probably the most useful part of this post.

When I connected my domain in Squarespace, it offered to set things up using its own nameservers ("Custom DNS"). It looked like the obvious, recommended path, so I went with it. That switched my domain's nameservers at Namecheap over to Squarespace.

The problem: all my Google Workspace email records live in Namecheap's DNS. Handing the nameservers to Squarespace meant the internet would stop looking there, and my email could stop arriving. That was the one thing I had promised myself would not happen.

How I recovered

As soon as I realized what I'd done, I asked Claude how to undo it. The fix took only a few minutes:

  1. Switch the nameservers back. In Namecheap, I set the nameservers back to Namecheap's own DNS.
  2. Check the email records survived. I looked at the DNS list in Namecheap to make sure all the email records were still there, and that the Google mail records were still listed. They were.
  3. Start clean in Squarespace. I disconnected the domain in Squarespace so I could redo the connection properly.
  4. Reconnect the right way. The second time, I read the screen more carefully. Next to the big "Get Started" button (the nameserver route) was a small option: "No, use DNS records". That path keeps the nameservers at Namecheap and just gives you a handful of records to add there.

What calmed me down was learning that email isn't lost during a short hiccup like this. If a sending server can't deliver, it keeps retrying for days. Act quickly, but don't panic.

Then I added the handful of records Squarespace listed in Namecheap, and within minutes Squarespace showed them all as found. I sent test emails in both directions. Everything worked.

Then I realized I had forgotten to publish the Squarespace site. Oops. One more click, and it was live.

What Claude was good at, and where it slipped

Claude was a patient teacher. It explained how long changes take to spread across the internet, and why to wait before changing anything, as many times as I asked. It caught my mistakes, like the record created under the wrong name. It kept a plan document up to date as we went, and it switched between English and Japanese whenever I did. While Claude worked, I'd often do something else in another window, and I was too lazy to switch my keyboard input back, so I just kept typing in whichever language I'd been using.

It wasn't perfect. It once wrote a wrong address into the plan, told me to test against the wrong Namecheap server, and read a stale cached result about my transfer lock. Each time it noticed and corrected itself quickly, but it's a good reminder: verify, don't just trust. That's exactly why the "run this and paste me the output" loop worked so well.

My personal take

My overall experience was great. From my three goals, plus the one thing I wanted to avoid, Claude put together a plan and a timeline: what had to happen, in what order, and when. That gave me the big picture of what I needed to do and a rough idea of how much time it would take. This isn't my job, so I had to fit everything into evenings and weekends, and I needed to know up front how much effort it would be. Above all, I needed to be sure my email wouldn't have any major downtime.

With that plan in hand, the actual work went smoothly, because Claude could explain anything that wasn't clear along the way. That mattered most where the labels didn't match from one system to the next. What helped me most, though, was being able to ask at any moment what a configuration change would affect, or what a term meant. I was never just blindly copying and pasting values into input fields. I could never have had a real person on hand like that, every time I needed help. And there was no rush: while I waited for Claude to answer, or for a change to take effect, I simply took my time and did other things.

Claude also checked the DNS settings with me at every step and pointed out anything that needed fixing right away. I never ended up wondering why my email had stopped arriving or why my website was unreachable.

In short: if you're facing a task like this, one you don't do every day, get Claude's help.

This article was drafted by Claude and reviewed and edited by me. The featured image was also created with Claude, using colors from one of my own paintings.

Next
Next

T-mobile international roaming is great!