Treat the website and mailbox separately
A custom app address and an email inbox use different DNS records; moving the website must not mean replacing the entire domain configuration. Overskill’s domain-limit article describes a per-app allowance and says a bare domain’s www address shares its slot. Its older tier names do not fully match the current pricing page, so confirm the allowance in your workspace rather than treating every table row as a current offer. No DNS change is required just to plan the connection.
Prepare an exact record checklist
Choose whether the app belongs on the main domain or a subdomain such as app.example.com. Inventory the existing record names and their purposes without copying secrets into a public document. Keep mailbox, verification and other-service records identified separately. When your platform supplies a target, compare the exact host name and value with the chosen app address. Do not borrow a target from another project or delete unfamiliar records because a setup guide shows a simpler example.
Verify more than the first page
After an authorized connection, check the secure address, a deep link and a signed-out page. Confirm that any callback or checkout address is the intended domain, not an old preview host. Test business email independently, because an app rendering successfully says nothing about mailbox delivery. Write down the prior website record and a recovery step before changing it. A DNS status badge is useful evidence of configuration, but the actual reader journey is the final check.
Keep a fallback address during transition
Retain the platform address until the custom domain works for the complete intended journey. Tell a small test group which address is authoritative so feedback does not mix two different versions. If the new address behaves inconsistently, stop broad promotion and inspect the specific mismatch rather than repeatedly rewriting records. This guide does not provide universal DNS values: those must come from your app’s current instructions and registrar. The aim is a controlled address change, not a domain-wide reset.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Overskill domain allowances — older tier labels — Merchant documentation · overskill.com · Merchant-controlled · checked 2026-09-18
- Overskill current pricing — Merchant documentation · overskill.com · Merchant-controlled · checked 2026-09-18