Domains
Table of Contents
Square Space
For a while, I registered my domains with Google Domains and used Google Domains DNS. In 2023, Google sold its domain registrar business to Square Space, and all my domains were migrated there.
Square Space charges more for the domains than Google Domains used to charge - and more than some registrars that sell domain registrations at cost do, which is a small problem.
Square Space does not support Dynamic DNS, which is a problem.
Some of my domains were imported into Google Cloud Domains at the time of migration; I did not get migration letters for them from Square Space, and they did not appear in the Square Space management UI, but the registrar for them did change to Square Space! This is a big problem, since I now can not manage those domains anywhere. I did not find any discussion of such a problem in Square Space help documents or anywhere else.
Which made me think: why don't I move all my domains to a different registrar?
Of course, I have no idea which ones are any good ;)
Cloudflare
A handy article Domain Registrars which Developers Recommend turned up; it seems that developers recommend Cloudflare, Namecheap, and Porkbun the most; Hover and Tucows much less.
Porkbun looks cool, but has to many pigs for my taste ;) It also seems to use Cloudflare DNS.
Cloudflare is very popular, supports Dynamic DNS, and probably has Terraform provider written for it, which I might find useful at some point. So, let's try it.
Of course, Square Space does not provide any way to export DNS settings, so there is going to be a lot of manual data recording and entering :(
And I really hope that Google Workspace services attached to some of my domains will not break :)
Let's go!
Migration
For each organization (dub@podval.org, dub@opentorah.org, dub@cognomath.org):
- sign up for Cloudflare using that org's admin Google email
- add billing
Documentation:
For each domain:
- old registrar: unlock
- old registrar: disable DNSSEC
- Cloudflare: add domain
- Cloudflare: verify DNS records:
- turn off proxying
- delete old name servers
- delete domainconnect record pointing to Square Space or Google
- delete Google domain verification record
- delete apex domain A records pointing to:
- Square Space (198.49.23.144 etc.)
- Google (216.239.32.21, 216.239.34.21, 216.239.36.21, 216.239.38.21, 2001:4860:4802:32::15, 2001:4860:4802:34::15, 2001:4860:4802:36::15, 2001:4860:4802:38::15)
- old registrar: replace name servers with the Cloudflare-assigned ones
- Cloudflare: notifies when the domain is active
- old registrar: get transfer authorization code
- Cloudflare: initiate transfer
Pulumi library
Three organizations use org.podval.tools:org.podval.tools.pulumi (github.com/dubinsky/pulumi, checkout
~/Podval/pulumi) from their infra repositories — GCP org, buckets, groups, and
Cloudflare DNS:
| Org | Checkout | Repo | Cloudflare account | Pulumi stack |
|---|---|---|---|---|
| Podval | ~/Podval/infra |
dubinsky/podval-infra |
dub@podval.org |
podval-infra / dev |
| OpenTorah | ~/OpenTorah/infra |
opentorah/infra |
dub@opentorah.org |
opentorah-infra / dev |
| CognoMath | ~/CognoMath/infra |
cognomath/infra |
dub@cognomath.org |
cognomath-infra / dev |
There is exactly one library checkout, ~/Podval/pulumi, and no symlinks. Each infra
settings.gradle defaults pulumiDir to ../../Podval/pulumi (i.e.
~/Podval/pulumi from ~/<Org>/infra; -PpulumiDir= overrides)
and composite-includeBuilds that directory when it exists. If that directory is missing,
Gradle resolves the published artifact from Maven Central. The same file includes the conventions build
from ../../Podval/podval-gradle (property podvalGradleDir) when that directory
is present. Published version is 0.5.0; local composite is 0.5.1 (alias /
Google-apex redirects).
Every zone also gets min_tls_version 1.2, DNSSEC, and CAA. Workspace zones (podval.org, opentorah.org, cognomath.org) get _dmarc
v=DMARC1; p=none with no rua (aggregate reports were too noisy); names without
mail get SPF -all and DMARC p=reject.
DnsZone patterns:
- GitHub Pages (
www→*.github.io): orange-cloud CNAME@→www→ GitHub + Always Use HTTPS (same asalter-rebbe.org). Extra CNAMEs stay DNS-only. Cloudflare terminates TLS (SSL Full, not strict). - Google Sites (
www→ghs.googlehosted.com): CNAME-flattened apex does not get a working HTTPS cert. Orange-cloud dummyA 192.0.2.1on@and a Single Redirect (http.host) tohttps://www.<domain>.wwwstays DNS-only to Google. - Auxiliary (
DnsZone.alias): orange-cloud dummy A on@andwww, Single Redirect to the canonicalhttps://www.<real>. The zone entrypoint ruleset is nameddefault(one per phase; renaming it 400s). Live auxiliary rulesets are still namedredirectexceptcognomath.org(default); PulumiignoreChangesonnamekeeps stacks clean. - GitHub apex → www, orange-cloud + Always Use HTTPS (
podval.org,opentorah.org,chumashquestions.org,mathworlds.org,alter-rebbe.org) - Google Sites apex → www (
cognomath.org) - auxiliary 301s:
podval.dev; OpenTorahopentorah.dev/chabad.dev/jewish-calendar.org; CognoMathcognomath.com.net.app.gamesand bothcongomath.* - MX / DKIM on Workspace zones (
smtp.google.com,google._domainkey) - DMARC: Workspace
_dmarcv=DMARC1; p=nonewith norua(aggregate reports were too noisy); mail-less names SPF-all+_dmarcp=reject - CAA
issue/issuewildforpki.googandletsencrypt.org - DNSSEC on every zone (
statusgoespendingthenactive; Cloudflare registrar publishes DS) -
min_tls_version1.2 on every zone - Voice number on registrar contacts (all three orgs)
- Square Space accounts deleted (registrar is Cloudflare)
- remove all mentions of domains etc. in all infrastructures and pulumi
Verified 2026-11-11. All 16 zones are on the Free plan. SSL is Full (not strict).
Always Use HTTPS, min_tls_version 1.2, DNSSEC active, and CAA are on
everywhere. Email Routing is unconfigured. No tunnels, no Pages projects, and R2 is not enabled on any
account.
Current state (podval)
Account dub@podval.org. Registrar for podval.org is Cloudflare (WHOIS);
zone metadata still remembers Squarespace as the previous registrar. Nameservers joel.ns.cloudflare.com / paislee.ns.cloudflare.com. Pulumi stack podval-infra / dev is clean.
| Zone | Role |
|---|---|
podval.org |
GitHub Pages, orange-cloud CNAME @ → www → dubinsky.github.io + Always Use HTTPS. Extra CNAMEs stay grey: Workspace calendar, docs, drive, email, groups,
hangouts, mail, sheets, slides → ghs.googlehosted.com (DNS-only), dub → GitHub Pages, nina →
ghs.google.com (Blogger), ha + its ACME name → Nabu Casa. |
podval.dev |
Auxiliary: dummy A + 301 → https://www.podval.org |
Dynamic DNS was configured for a while. A Cloudflare A record pointed at the house, and an LXC on [[ProxMox]] updated it. Nothing used it. It is gone, in favour of Tailscale.
http://www.podval.org/ is now Cloudflare Always Use HTTPS (301 to https://).
Current state (OpenTorah)
Account dub@opentorah.org. Pulumi stack opentorah-infra / dev
is clean. opentorah/opentorah Pages custom domain is only www.opentorah.org
(not jewish-calendar.org).
| Zone | Role |
|---|---|
opentorah.org |
GitHub Pages, orange-cloud + Always Use HTTPS, same as alter-rebbe.org |
chumashquestions.org |
GitHub Pages, orange-cloud + Always Use HTTPS. Single Redirect /book.pdf → https://www.chumashquestions.org/book/book.pdf (301); ruleset named default. |
alter-rebbe.org |
GitHub Pages, orange-cloud + Always Use HTTPS; extra app → Workspace, store/facsimiles → GCS |
opentorah.dev, chabad.dev, jewish-calendar.org |
Auxiliary: dummy A + 301 → https://www.opentorah.org |
Worker alter-rebbe-aliases and its routes on www.alter-rebbe.org (about 51
patterns: archive prefixes lvia*, niab*, rgia*, plus /search*, /name*, /map*) are deployed by site-publisher.yml in opentorah/alter-rebbe.org, not by Pulumi.
No Blogger ghs.google.com. No Dynamic DNS A records.
Current state (CognoMath)
Account dub@cognomath.org. Pulumi stack cognomath-infra / dev
is clean (redirect ruleset for cognomath.org is the zone entrypoint named default).
| Zone | Role |
|---|---|
cognomath.org |
Google Sites www → ghs.googlehosted.com; apex dummy A + 301 → https://www.cognomath.org. Extra: blog → blog.cognomath.org.ghs.googlehosted.com, games/treasure-hunt →
GCS. MX/DKIM as usual. |
mathworlds.org |
GitHub Pages (cognomath.github.io), orange-cloud + Always Use HTTPS |
cognomath.com .net .app .games, congomath.org .com |
Auxiliary: dummy A + 301 → https://www.cognomath.org |
API tokens
Do not put token values here.
Pulumi tokens (~/Podval/Keys/podval-cloudflare-api-token.txt, ~/OpenTorah/Keys/opentorah-cloudflare-api-token.txt, ~/CognoMath/Keys/cognomath-cloudflare-api-token.txt) are account-owned
(user-token verify 401; account-token verify 200). That is the right kind for automation — keep them; do
not switch to user tokens. Each .envrc sets CLOUDFLARE_API_TOKEN. Grants are
consistent enough to run DnsZone: Zone DNS Edit, Zone Edit, Zone Settings Edit, and Single
Redirects (rulesets work). GET /zones also reports #waf:edit / Page Shield /
SSL Read — WAF package APIs 403, tunnels list as empty 200; those are not extra checkboxes that matter.
Page Rules API returns 1011 for the account-owned Pulumi tokens; a user-level OAuth connection returns
an empty list (no page rules on any zone). Unused (Single Redirects instead).
All three Pulumi tokens can PATCH always_use_https (CognoMath used to 403; it no longer
does). CognoMath can also read Universal SSL / certificate packs; Podval and OpenTorah 403 those — extra
on CognoMath, not required. No expiry.
Other tokens:
- OpenTorah worker token: GitHub Actions on
opentorah/alter-rebbe.orgdeploys Workeralter-rebbe-aliases(site-publisher.yml→ repo secretCLOUDFLARE_API_TOKEN). The live Worker does not use the token; only redeploy does. Local copy:~/OpenTorah/Keys/alter-rebbe-org-cloudflare-worker-api-token.txt. Account token UI (2026-09): Manage Account → Account API Tokens. Workers grant is role Editor on Specified Workers →alter-rebbe-aliases(legacy name was Account → Workers Scripts → Edit). Also Zone → Workers Routes → Write onalter-rebbe.org. Put the value in both the Keys file and that GitHub secret. Do not reuse the Pulumi token.
Dynamic DNS
This ran for a while: a Cloudflare A record, and an LXC on [[ProxMox]] that updated it. Nothing used it. It is gone, in favour of Tailscale.
Among other interesting things, CloudFlare does support Dynamic DNS.
I am running UniFi, which does have some sort of Dynamic DNS update facility, but it seems to have issues with CloudFlare.
Apparently, [[Home Assistant]] can do it also - but why bother? I am running [[ProxMox]], so adding a dedicated Dynamic DNS client seems the way to go ;)
I found a nice CloudFlare DDNS updater - with the additional attraction that its author, favonia, is familiar from the HoTT scene :)
I thought that the client is not available as a ProxMox LXC container. Since I have virtual machine for
running Docker containers, I can use that to run it with Docker or Docker compose. After testing it with
Docker, I configured a docker-compose.yaml and started it with docker compose up
-d. Here is docker-compose.yaml:
services:
cloudflare-ddns:
image: favonia/cloudflare-ddns:latest
network_mode: host
restart: always
read_only: true
cap_drop: [all]
security_opt: [no-new-privileges:true]
environment:
- CLOUDFLARE_API_TOKEN=...
- DOMAINS=<the house name>
- IP6_PROVIDER=none
Turns out, the client is available as an LXC after all, and that is how I ran it until 2026-11-18.
Until then the binary was favonia cloudflare-ddns 1.18.0 at /usr/local/bin/cloudflare-ddns. It had been extracted from the official image ghcr.io/favonia/cloudflare-ddns:1.18.0, not built on the LXC. go run …@latest
filled the 3G disk once. Do not bring the container back.
Remote SSH (not Cloudflare Tunnel)
On the LAN, SSH is ssh pve / ha / frigate / unifi, with the [[Yubikey: 2-factor authentication (U2F, OATH and OTP)
and SSH]]. Dynamic DNS used to publish a name for the house. Nothing used it. It is gone, in favour
of Tailscale. Port 22 is not published on the router. Checked 2026-11-18: there are no port-forward
rules.
Remote access is a [[ProxMox]] container running Tailscale. It is not
an exit node, and Tailscale SSH is off, so admin login stays normal SSH plus the YubiKey. Checked
2026-11-18: that container still advertises one subnet route, and the route is enabled. My own machines
off the LAN accept it and use the same ssh aliases as on the LAN. That route is not the
assistant path. Grok Bot comes in as a forwarding-only user on the same container, and that user can
open SSH only on a short allow-list. Assistant access is [[Grok Bot
Access]].