Cloudflare (DNS + CDN)¶
Genji Shimada uses Cloudflare for DNS, TLS, and CDN delivery. This page captures the relevant records and R2/CDN settings used by the stack.
Zones¶
bkan0n.comgenji.pk
Both zones are proxied through Cloudflare. The origin IP is intentionally omitted from docs; store it in your private ops notes.
DNS Records (Relevant Only)¶
Only records used by Genji Shimada and related infrastructure are listed below.
bkan0n.com¶
bkan0n.com(A, proxied) -> origin IP (private)auth.bkan0n.com(CNAME, proxied) ->bkan0n.comportal.bkan0n.com(CNAME, proxied) ->bkan0n.comgrafana.bkan0n.com(CNAME, proxied) ->bkan0n.comprometheus.bkan0n.com(CNAME, proxied) ->bkan0n.comloki.bkan0n.com(CNAME, proxied) ->bkan0n.comalloy.bkan0n.com(CNAME, proxied) ->bkan0n.comcadvisor.bkan0n.com(CNAME, proxied) ->bkan0n.comstatus.bkan0n.com(CNAME, proxied) ->bkan0n.comtranslate.bkan0n.com(CNAME, proxied) ->bkan0n.comdockhand.bkan0n.com(CNAME, proxied) ->bkan0n.comcdn.bkan0n.com(CNAME, proxied) ->public.r2.dev
genji.pk¶
genji.pk(A, proxied) -> origin IP (private)api.genji.pk(CNAME, proxied) ->genji.pkdev-api.genji.pk(CNAME, proxied) ->genji.pkdev.genji.pk(CNAME, proxied) ->genji.pkrabbitmq.genji.pk(CNAME, proxied) ->genji.pkdev-rabbitmq.genji.pk(CNAME, proxied) ->genji.pkdb.genji.pk(CNAME, proxied) ->genji.pkdocs.genji.pk(CNAME, proxied) ->genjishimada.github.iocdn.genji.pk(CNAME, proxied) ->public.r2.dev
SSL/TLS¶
- Mode: Full
R2 Buckets and CDN¶
Public CDN domains:
cdn.bkan0n.comcdn.genji.pk
Buckets in use:
genji-db-backupsgenji-parkour-images
R2 CORS Policy¶
Allowed origins:
http://genji.testhttps://dev.genji.pkhttps://genji.pkhttp://localhost:3000
Allowed methods: GET, HEAD
Allowed headers: *
R2 Response Headers¶
For wildcard hostnames *.bkan0n.com and *.genji.pk:
Cross-Origin-Resource-Policy: cross-originVary: Origin, Access-Control-Request-Method, Access-Control-Request-Headers
Related Docs¶
- Reverse Proxy - Caddy routing and TLS automation
- Monitoring - Grafana/Prometheus/Loki endpoints