Domains and Deployments

Outcome

You will know how to frame hosted domain and deployment work inside TMXIO and what to verify before and after a change.

Before You Start

Have the target environment, expected domain, and rollout window in hand. A surprising number of deployment mistakes are just environment mix-ups, so read the environment label on every screen before you click anything destructive.

Typical Deployment Questions

• Which environment should receive this change first?
• Is the domain already pointed where it needs to point?
• If something goes wrong, do we need rollback guidance ready?

The Deployment Loop

The hosted deployment flow is a short loop: change, validate, promote, verify. If something fails, you roll back and investigate before retrying. The diagram below shows the path most teams follow.

flowchart LR
  A[Edit content] --> B{Staging build}
  B -->|pass| C[Promote to production]
  B -->|fail| D[Investigate logs]
  C --> E{Production healthy?}
  E -->|yes| F[Done]
  E -->|no| G[Roll back to previous build]
  G --> D

Recommended Operating Pattern

1. Validate in the non-production environment when practical. Most surprises surface in staging, where they are cheap to fix.

2. Confirm the domain and environment you are about to touch. Read the environment label twice if you are about to promote.

3. Run the planned deployment or cutover during your agreed rollout window.

4. Check that the site responds correctly and the expected domain is serving the right version. Test from a fresh browser session, not a cached tab.

DNS changes do not propagate instantly

When you change a DNS record, expect a propagation lag from a few minutes up to a full TTL window. During that window, some visitors will see the old destination and some will see the new one. Plan domain cutovers outside peak traffic and lower the TTL ahead of time when you can.

When to roll back instead of fix forward

If a production deployment is causing visible customer impact, roll back to the previous build first and investigate afterward. Rolling back is almost always faster than diagnosing a live issue, and it gives you a clean state to compare against once you start looking at logs.

What Success Looks Like

• The intended environment receives the change.
• The expected domain resolves to the right site experience.
• The team knows whether follow-up monitoring is required.

Related Troubleshooting

• Use Hosted Troubleshooting if a deployment appears healthy in TMXIO but the site does not reflect the expected change.