DNS after checkout: pointing your domain at new hosting

Checkout creates the hosting account. DNS is what makes the hostname resolve to it. If the domain is already at Vioflare, change the records in the portal; if it sits at another registrar, create or update the A and AAAA records there — plus MX, if your mail is moving too.

Key takeaways

  • A new hosting account does nothing until DNS points at it.
  • Changing A and AAAA is the fastest, lowest-risk route for most customers.
  • Changing nameservers hands the whole zone to one DNS host — more powerful, more to get wrong.
  • Web and mail are separate records. Moving the site does not move the mailboxes.
  • Lower the TTL a day ahead, and verify with dig and curl rather than by refreshing the browser.

Steps

  1. Find the server IP in the client portal under your service details, after provisioning completes.
  2. Lower the TTL on the records you are about to change to 300–600 seconds, a day ahead.
  3. Get the site working on the new server first, using a temporary hostname or a local hosts entry.
  4. Update the A record (and AAAA, if you have one) to the new IP at whichever DNS host is authoritative.
  5. Update MX, SPF and DKIM only if mail is also moving to Vioflare.
  6. Verify resolution and the certificate with dig yourdomain.com.au +short and curl -I https://yourdomain.com.au/.
  7. Raise the TTL again once the site and mail have been stable for a day.

A record change or nameserver change?

Approach When to use it
Change A / AAAA (and MX) only The domain stays at another registrar or DNS host. Fastest and most surgical for most customers.
Change nameservers You want the whole zone managed in one place, at the host that issued them.
Leave DNS alone The domain is already at Vioflare and the records were set at provisioning.

A record change touches only what you name. A nameserver change moves the entire zone, so every record that existed at the old DNS host must be recreated at the new one before you switch — including mail, verification TXT records and any subdomains. That is the step people forget, and it is why the surgical option is usually the right one.

Which records do what

Record Controls Change it when
A IPv4 address of the website The site moves servers
AAAA IPv6 address of the website The site moves servers
MX Where inbound mail is delivered Mail hosting moves
TXT (SPF) Which servers may send as your domain Your sending host changes
TXT (DKIM) Signing key for outbound mail Your sending host changes
CNAME Alias, e.g. www or webmail You add a subdomain

The common accident is changing A for a site move and assuming mail followed. It did not. If the mailboxes are staying put, leave MX, SPF and DKIM exactly as they are.

Keeping integrations and AI agents online

Anything that calls your domain by name needs the name to resolve to the new server, and anything that calls you needs its callback URL to be right:

  • Webhooks and callbacks in payment providers, Slack, n8n and automation tools.
  • Scheduled jobs or agents that fetch a URL on your domain.
  • API clients pinned to a hostname rather than an IP.
  • TLS certificates, which may need reissuing after an IP change — free SSL is included on every plan, see free SSL.

Check these before the cutover, not after. A webhook that silently fails for a day is harder to notice than a website that is down for ten minutes.

Verify the cutover properly

Browsers cache aggressively and will lie to you. Use the tools instead:

  • dig yourdomain.com.au +short — confirms the A record the resolver sees.
  • dig MX yourdomain.com.au +short — confirms mail still points where you intended.
  • curl -I https://yourdomain.com.au/ — confirms the new server answers and the certificate is valid.

If dig shows the new IP and curl returns a clean 200, the cutover worked regardless of what any one browser shows.

Frequently Asked Questions

Where do I find the IP address to point my domain at?

In the client portal, under the service details for your new hosting account, once provisioning has finished. The hosting plans page explains what each plan provisions.

Can I keep email with Google or Microsoft while the site is on Vioflare?

Yes. Change only the A and AAAA records for the website and leave the existing MX, SPF and DKIM records untouched. The two services are independent.

How long does DNS propagation take?

It follows the TTL you had set before the change, which is why lowering it a day ahead matters. With a short TTL most resolvers pick up the new value within minutes.

Should I change nameservers or just the A record?

Change the A record if the domain's DNS is managed somewhere you are happy with. Change nameservers only when you want the whole zone moved, and recreate every existing record first.

My site loads but the browser warns about the certificate — why?

The certificate has not yet been issued or reissued for the new server. Free SSL is included on every plan; see free SSL for how issuance works once DNS points at the right place.