rruki.zone
All guides
Infra#infra#dns#self-hosting

Organizing Everything on Subdomains

How I use *.ruki.zone to keep socials, services, and projects tidy and memorable.

September 10, 20261 min read

One domain, many doors

I treat ruki.zone as a hub and give everything else its own subdomain. It keeps URLs short, memorable, and easy to reason about.

The pattern

  • Socials live at {social}.ruki.zone — like github.ruki.zone.
  • Services live at {service}.ruki.zone — like status.ruki.zone.
  • Projects get a product subdomain when they graduate from experiment to real thing.
SubdomainPoints to
go.ruki.zoneShort-link redirector
status.ruki.zoneUptime monitor
cdn.ruki.zoneStatic asset host

Why it works

Each subdomain is independently deployable and swappable. If I change short-link providers, only go.ruki.zone moves — nothing else on the zone notices.

A note on redirects

For socials I usually just set up a redirect so github.ruki.zone sends people to my actual profile. It's branded, it's mine, and I can move it whenever I want.