I Bought My Brother a Domain Name

Sometimes the best technology projects aren't the ones with the most Docker containers, the fastest hardware, or the most complicated setup. Sometimes it's buying a domain name, building a website, setting up an email address, and sending your brother a link he wasn't expecting.

William

9/3/20265 min read

It's been a while since I've written anything for MotoLinux.

That doesn't mean I haven't been doing anything.

Quite the opposite, actually.

If you've followed this site for any length of time, you probably know that I have a bad habit of finding projects for myself. Linux servers, self-hosted services, networking, AI, Raspberry Pis, old computers that probably should have been recycled years ago...

There is always something.

Most of these projects start with a simple idea.

"I wonder if I can do that myself?"

And then, several hours later, I've somehow created a problem that requires three containers, a reverse proxy, DNS changes, and a spreadsheet.

This particular project started differently.

I decided to buy my brother a domain name.

Blue Ribbon Auto Care Gets Its Own Corner of the Internet

My brother owns an automotive repair business called Blue Ribbon Auto Care in Collegeville, Pennsylvania.

At some point, I started thinking about the fact that I have spent a ridiculous amount of time learning how to run websites, manage servers, configure services, and generally make computers do things.

Meanwhile, my brother had a business that could benefit from having its own proper home on the internet.

So I checked to see if the domain was available.

It was.

A few minutes later, I owned:

blueribbonautocare.com

Now, technically, buying a domain name isn't exactly difficult.

You give someone money and they give you a name.

The interesting part is what happens after that.

"I'll Just Put Together a Simple Website"

Those are dangerous words.

Anyone who has ever worked in IT, built a computer, configured a server, or remodeled part of their house knows exactly what happens next.

You start with something simple.

Then you think:

"Well, while I'm doing this..."

And before long, your "simple website" has turned into an actual project.

I put together a basic website for Blue Ribbon Auto Care.

The goal wasn't to build the next Amazon or redesign the entire automotive industry. I just wanted to give the business a professional presence online.

Somewhere people could go to learn about the shop.

Somewhere they could find contact information.

Somewhere that actually belonged to the business.

Of course, a domain name also means you can do something else useful with it.

Email.

So I set that up too.

Because if you're going to own blueribbonautocare.com, you might as well be able to send email from it.

Then I Sent Him the Link

This was probably my favorite part of the entire project.

I didn't make a big announcement.

I told him I had been working on something but didn't say what it was.

I just sent him the link.

And waited.

His reaction was better than I expected.

He was impressed by the website, but I think he was also genuinely touched that I had done it for him.

I've built plenty of things over the years. I've installed operating systems more times than I can count. I've built computers, maintained servers, configured networks, and spent more time troubleshooting technology than I probably care to admit.

But this project was different.

This wasn't something I built because I needed another server running in my house.

Nobody was going to ask me what version of Docker I was using.

There wasn't a dashboard involved.

Okay, there may have been a dashboard involved somewhere, but that's not the point.

The point was that I was able to use things I've spent years learning to do something useful for someone else.

And apparently, I managed to surprise my brother in the process.

Of Course, I Couldn't Leave It Alone

The website was never really going to be a "build it once and never touch it again" kind of project.

That's just not how I work.

Once something is up and running, I immediately start noticing things that could be improved.

Maybe this could be easier.

Maybe that would look better.

Maybe there should be a better way to do this.

Maybe I should change something that nobody else has noticed.

And so the project has continued.

I've made a number of quality-of-life improvements to the site since it first went live. Nothing earth-shattering, but the kind of changes that make a website feel more polished and useful.

And then I had another idea.

What If We Updated the Logo?

Blue Ribbon Auto Care already has a logo.

But I started thinking about what we could do if we gave the business a new visual identity.

Not necessarily something overly corporate or generic.

I wanted something with some personality.

The idea I came up with was a stylized spark plug character holding automotive tools.

Something that immediately says "automotive" but is also memorable.

Something that could work on the website, but also on shirts, hats, stickers, invoices, cups, and whatever else we might come up with later.

And naturally, because it's 2026 and I apparently can't leave well enough alone, that idea has turned into another opportunity to experiment with AI image generation.

So now a simple domain name has somehow led to a website, business email, ongoing improvements, branding discussions, and a possible spark plug mascot.

That escalated quickly.

Why This Project Means Something to Me

I think one of the reasons I enjoy technology is because there is always something new to learn.

You can start with one thing and it leads you somewhere else.

I started using Linux because I was curious.

That eventually led to servers.

Then networking.

Then self-hosting.

Then domains.

Then VPS servers.

Then Docker.

Then AI.

And probably another dozen things I'm forgetting.

Sometimes, though, it's easy to get caught up in the technology itself.

It's easy to spend hours debating which Linux distribution is better, whether something should run in a container, or whether you really need another computer running 24 hours a day.

For the record, the answer to that last question is usually no.

But sometimes you buy another one anyway.

This project reminded me that all of those things I've learned over the years can occasionally be used for something more than satisfying my own curiosity.

Sometimes they can actually help someone.

In this case, it was my brother.

I bought a domain name.

I built a website.

I set up an email account.

Then I sent him a link.

That's it.

More to Come

Blue Ribbon Auto Care is still a work in progress.

The website will continue to evolve, and we'll see where the logo idea goes. I already have a few ideas, and knowing myself, there's a pretty good chance this project will continue to grow into something much larger than I originally intended.

Because apparently I have a history of doing that.

But that's okay.

Some projects are worth getting carried away with.

And this one started with something pretty simple.

I bought my brother a domain name and built a website.

He liked it.

And that made the whole thing worth it.

MotoLinux

Dive into open-source and technology insights here.

Community

Innovation

contact@motolinux.com

© 2026 MotoLinux. All rights reserved.