Use AI for a cutover checklist if you like — keep DNS TTL, auth codes, and nameserver timing as human decisions so email and AI webhooks stay up.
Transfer a .com.au domain without downtime
Keep the existing nameservers through the registrar move, and nothing goes down. A transfer changes who manages the domain, not where it points — the outages people blame on transfers are almost always a DNS change made at the same time.
Key takeaways
- A registrar transfer and a DNS change are two separate jobs. Do them in that order, not together.
- Record your current nameservers, A, AAAA and MX records before you start.
- Lower TTL a day ahead so any later change propagates in minutes rather than hours.
- You need the domain unlocked and an EPP (auth) code from the losing registrar.
- Approve the confirmation email promptly; an unanswered confirmation is the most common stall.
Steps
- Record the current nameservers plus every A, AAAA, MX and TXT record, and keep that list open.
- Lower the TTL on those records to 300–600 seconds at least a day before the cutover.
- Unlock the domain at the current registrar and clear
clientTransferProhibitedif it is set. - Request the EPP or auth code from the current registrar, and check the registrant email on file still reaches you.
- Start the transfer on the domain transfer page and enter the auth code.
- Approve the confirmation or Form of Authorisation message as soon as it arrives.
- Leave DNS alone until the transfer completes and the domain shows in your account.
- Only then change A, AAAA or MX records, if you are also moving hosting — and raise the TTL again once mail and the site have been stable for a day.
Why the order matters
Nameservers travel with the domain, not with the registrar. If you leave them pointed at the old DNS host, the website and the mailboxes keep resolving exactly as before while the registration moves underneath them. Visitors see nothing.
Change the nameservers in the same window and you have two variables moving at once. If something breaks you cannot tell whether the transfer or the DNS change caused it, and you are debugging under pressure with a long TTL working against you.
Before you start: the things that actually block transfers
- Registrant email. The confirmation goes to the address on the domain's record, not to whoever is doing the work. Check it first.
- Transfer locks. A domain registered or transferred very recently may be locked. Check the current registrar's status before you plan a date.
- Expiry date. Starting a transfer days before expiry is avoidable risk. Renew first, then move.
- Pending changes. A transfer requested while another change is in flight will often simply fail.
What checklists generated by AI tools tend to miss
A chatbot can draft the generic steps. It cannot see your panel, your TTL or your DNS zone, and these are the items that actually bite:
- Mail left pointing at the old host after the web A record changed. Web and mail are separate records; moving one does not move the other.
- Webhooks still calling the old hostname — Stripe, n8n, payment providers and any integration that posts to your site.
- TLS certificates that need reissuing after an IP change, so the site loads but the browser warns.
- SPF and DKIM records that were never copied across, which turns into a deliverability problem a week later rather than an outage on the day.
- A second, forgotten zone at the old DNS host that keeps answering for a subdomain.
Work from your own recorded zone file, not from a generic list.
Moving the hosting as well
If the point of the exercise is to move the site too, do it as two scheduled changes:
- Transfer the registrar. Confirm the domain is in your account and DNS is untouched.
- Provision the new hosting plan and get the site working on its new server before any public DNS points at it.
- Change the A and AAAA records in a planned window, with TTL already low.
- Change MX separately, if mail is moving, and verify both directions with a test message.
Website migration covers the hosting side, and DNS after checkout covers which records to set once the new account exists.
Frequently Asked Questions
Will transferring my domain take my website offline?
No, provided you leave the nameservers unchanged during the registrar move. The domain keeps resolving to the same DNS host and the same server throughout.
How long does a .com.au transfer take?
Usually a short wait once the auth code is accepted and the confirmation is approved, though it depends on the losing registrar's processing. Delays are nearly always an unapproved confirmation email.
What is an EPP or auth code?
It is the transfer authorisation code held by your current registrar, proving you control the domain. You request it from them and enter it when you start the transfer at the new registrar.
Can I transfer a domain that is about to expire?
It is far safer to renew first and transfer afterwards. A transfer begun close to expiry can fail and leave you renewing in a hurry at the old registrar anyway.
Do I need to tell my email provider about the transfer?
Not for the transfer itself, since MX records do not change. You do need to tell them if you later move mail hosting, which is a separate DNS change.

