ALAI Domain Migration — basicconsulting.no → alai.no ALAI Domain Migration — basicconsulting.no → alai.no Context ALAI rebrand did not include support stack migration. 11 subdomains remain on legacy basicconsulting.no domain. Current Live State (by Zone) basicconsulting.no (Cloudflare zone 4670dbd0acfeab4174ac0d4746d11ea0) 30+ DNS records Main support stack hosting Active services: docs, sign, bilko-demo, www Inactive subdomains: status, support, monitor, alerts, help, wiki alai.no (Cloudflare zone 3dc40d9c37fee79c4281f7e86870c0b5) Status: PENDING — Nameservers on one.com not yet changed Required NS change: ns01/02.one.com → aspen.ns.cloudflare.com + wells.ns.cloudflare.com 18 DNS records pre-created (A/CNAME for 15 services + root) Blocker: Alem must update NS on one.com dashboard (5 min task, blocks 15 subdomain migrations) snowit.ba (AWS Route53 zone Z04121493CAJZ75TQUPIW) 2026-04-19 added: A record root → 76.76.21.21 (Vercel) CNAME www → cname.vercel-dns.com Change ID: C065644119MEENZWSSKW3 Cloudflare Tunnel Config Tunnel ID: 3315a609-7934-45c5-ad0c-56d86d16374d (named "mattermost") Host VM: Azure 4.223.110.181 (swedencentral) Ingress rules: Multiple service routes (see tunnel config for details) Incident: sign.basicconsulting.no 404 (2026-04-18) Symptom: DNS resolved to Cloudflare proxy but returned 404. Root cause: Tunnel ingress had route sign.basicconsulting.no → localhost:3003 but cloudflared could not reach backend. Fix: Changed DNS from tunnel CNAME to direct A record → 4.223.110.181 (proxied). Result: Documenso Sign In page now live. Alem TODO Log into one.com domain panel Select alai.no domain Change nameservers from ns01/02.one.com to: aspen.ns.cloudflare.com wells.ns.cloudflare.com Wait 5-30 minutes for propagation Verify: dig alai.no NS should show Cloudflare nameservers See Also Documenso Self-Hosted BookStack runbooks Created: 2026-04-19 | Source: ~/ALAI/products/Bilko/docs/runbooks/alai-support-stack-migration.md