Cloudflare manages DNS for yhkze.net. The server’s
public IP is the single A record at the apex; services are CNAMEs
pointing at it, except those reachable only over WireGuard (reference Services — WireGuard Only).
Proxied vs DNS-only:
| Record | Type | Value | Proxy |
|---|---|---|---|
yhkze.net |
A | server public IP | Proxied |
www.yhkze.net |
CNAME | yhkze.net |
Proxied |
These all resolve to the server IP via Cloudflare:
| Subdomain | Service |
|---|---|
argocd.yhkze.net |
ArgoCD GitOps UI |
kargo.yhkze.net |
Kargo promotion UI |
mem.yhkze.net |
Memos note taking |
n8n.yhkze.net |
n8n workflow automation |
rgxr.yhkze.net |
rgxr (K8s app) |
rgxr-test.yhkze.net |
rgxr staging |
rss.yhkze.net |
Miniflux RSS reader |
search.yhkze.net |
SearXNG search engine |
slskd.yhkze.net |
slskd Soulseek client |
ssh-tunnel.yhkze.net |
wstunnel SSH-over-HTTPS bridge |
tmp.yhkze.net |
Temporary services / staging |
vault.yhkze.net |
OpenBao secret management |
Direct IP — Cloudflare proxy disabled:
| Subdomain | Service | Reason |
|---|---|---|
anki.yhkze.net |
Anki sync server | Client-cert pinning, non-browser |
chat.yhkze.net |
Open WebUI chat interface | Long-running requests, document uploads, reference Proxy latency |
cloud.yhkze.net |
OpenCloud file sharing | Video streaming and file transfer, reference Proxy latency |
git.yhkze.net |
Forgejo Git hosting | HTTPS clones, pushes and LFS above the 100 MB body limit, reference Proxy latency |
hari.yhkze.net |
Perses dashboards | OIDC sign-in redirect chain, and every panel is its own query, reference Proxy latency |
id.yhkze.net |
Keycloak identity provider | Sequential redirects in every OIDC login and token refresh, reference Proxy latency |
mail.yhkze.net |
Mail server | SMTP port 25 is blocked by Cloudflare proxy |
mc.yhkze.net |
Minecraft server | TCP 25565, not HTTP |
music.yhkze.net |
Navidrome music server | Audio streaming, Subsonic clients chain API calls, reference Proxy latency |
notes.yhkze.net |
Trilium notes | Client sync chains many requests, reference Proxy latency |
office.yhkze.net |
Collabora Online | Interactive editing inside OpenCloud, reference Proxy latency |
ssh-git.yhkze.net |
Forgejo SSH | TCP 30354, not HTTP |
sso.yhkze.net |
oauth2-proxy forward auth | Redirect chain to Keycloak and back, reference Proxy latency |
wg.yhkze.net |
WireGuard VPN | UDP 30352, not HTTP |
An A record holding the server’s WireGuard address, DNS only. Any
peer reaches Traefik over wg0 from whatever network it is
on, phone included, and Traefik’s wireguard-only middleware
refuses every source outside 10.100.0.0/24. A device
without WireGuard cannot reach the service, at home or elsewhere:
| Record | Type | Value | Service | Reason |
|---|---|---|---|---|
alerts.yhkze.net |
A | 10.100.0.1 |
Alertmanager UI (Keycloak sign-in) | Silences every alert; reference Observability |
id-admin.yhkze.net |
A | 10.100.0.1 |
Keycloak admin console and REST API | Administers every identity; reference Keycloak |
inv.yhkze.net |
A | 10.100.0.1 |
Invidious YouTube frontend | Every watch page is a YouTube request through the Mullvad relays; a
crawler ignoring robots.txt got them refused, reference Invidious |
Proxied traffic leaves for the nearest Cloudflare edge (Miami) and comes back to the server, so every request pays that round trip twice. Measured on 2026-11-13 from a remote client, before and after moving each host to DNS only. Time to first byte is the median of five fresh connections, per request is the mean over one reused connection, and throughput downloads each host’s largest static asset uncompressed:
| Host | First byte, proxied | First byte, direct | Per request, proxied | Per request, direct | Throughput, proxied | Throughput, direct |
|---|---|---|---|---|---|---|
auth |
0.45 s | 0.04 s | 132 ms | 12 ms | 1.4 MB/s | 5.0 MB/s |
chat |
0.40 s | 0.04 s | 140 ms | 16 ms | 0.5 MB/s | 1.9 MB/s |
git |
0.43 s | 0.04 s | 123 ms | 10 ms | 2.0 MB/s | 6.3 MB/s |
inv |
0.45 s | 0.04 s | 137 ms | 10 ms | 0.2 MB/s | 0.8 MB/s |
music |
0.27 s | 0.04 s | 134 ms | 10 ms | 4.7 MB/s | 8.8 MB/s |
notes |
0.43 s | 0.04 s | 126 ms | 14 ms | 0.04 MB/s | 0.16 MB/s |
office |
0.44 s | 0.04 s | 128 ms | 10 ms | 5.6 MB/s | 9.5 MB/s |
Small assets (inv, notes,
chat) show latency rather than bandwidth. The penalty is
the same on every proxied host, so it matters where a page or client
chains many requests or moves bulk data: media range requests, OIDC
redirect chains, sync protocols, git transfers. The free proxy also caps
request bodies at 100 MB, ends requests that take longer than 100 s with
error 524, and its terms restrict serving mostly video or audio. Going
direct gives up Cloudflare’s DDoS protection and edge cache for that
host; the protection was already partial, since Traefik answers every
host on the published server IP.
The comparison command forces the direct path with
--resolve and needs no DNS change:
u=https://cloud.yhkze.net/<static asset path>
curl -s -o /dev/null -w "%{time_starttransfer} %{speed_download}\n" "$u"
curl -s -o /dev/null -w "%{time_starttransfer} %{speed_download}\n" --resolve cloud.yhkze.net:443:<server public IP> "$u"| Record | Type | Value |
|---|---|---|
yhkze.net |
MX (priority 10) | mail.yhkze.net |
_dmarc.yhkze.net |
TXT | v=DMARC1; p=quarantine; rua=mailto:[email protected] |
yhkze.net |
TXT | v=spf1 mx include:spf.smtp2go.com ~all |
mail._domainkey.yhkze.net |
TXT | DKIM public key (reference Mailserver) |
em962084.yhkze.net |
CNAME | return.smtp2go.net |
link.yhkze.net |
CNAME | track.smtp2go.net |
s962084._domainkey.yhkze.net |
CNAME | dkim.smtp2go.net |
The DKIM key is auto-generated by the mailserver at
/var/dkim/ — reference Mailserver for how to retrieve it
after initial deploy.
The three CNAME records serve the SMTP2GO outbound relay (return-path, click tracking, DKIM) — reference Mailserver. All DNS-only.
| Record | Type | Value | Used by |
|---|---|---|---|
yhkze.net |
TXT | google-site-verification=SZSgwVDQ6tgteAxE0bLJTGqJbmyvZpDtVjpwHF75iTU |
Google Search Console (Domain property) |
The record must stay for as long as the Search Console property is in
use: Google re-checks it periodically and drops the verification when it
disappears. It sits next to the SPF TXT record at the apex; mail servers
only read the record starting with v=spf1, so both
coexist.
yhkze.net → DNS → Records
→ Add recordCNAME, Name: <subdomain>,
Target: yhkze.net