Have you received an email like this?
“Our records indicate that the ABN/ACN currently associated with XYZ.com.au is not eligible to hold this domain name. Action is required, or the domain may not be eligible for renewal.”
If you’ve recently received a message like this and are feeling confused — you’re not alone.
At CommandHost, we manage domain registrations and renewals for our customers. Recently, many of our clients have reached out with concerns about eligibility warnings related to their .au domain name registrations.
Here’s what’s going on, and what you need to do to stay compliant with auDA’s updated rules.
What’s Changed?
.au Domain Administration (auDA), the body that sets the rules for all Australian domain names, has tightened its eligibility requirements — especially for domains registered using Trust ABNs, such as those from Discretionary Trusts.
Key change:
Domains registered with a Discretionary Trust ABN are no longer considered valid unless the ABN belongs to the Trustee, not just the Trust.
According to auDA Registrar Rules Section 2.9.1:
-
The Registrant is the legal entity that holds the domain licence — this must be the Trustee, not the Trust itself.
-
The Eligibility ID is the ABN, ACN, or other identifier used to demonstrate the Registrant’s eligibility — and this ID must belong to the Trustee.
If your domain was registered using:
-
A Company or Sole Trader ABN/ACN → ✅ No action needed
-
A Discretionary Trust ABN without the Trustee properly identified → ⚠️ Action required
How Can I Check My Domain’s ABN?
You can check the ABN linked to your domain at: https://whois.auda.org.au
Search for your domain and look for:
-
Registrant ID: This is the ABN currently linked to your domain (your Eligibility ID under auDA rules).
-
Eligibility Type: If it says Discretionary Trust or Trust, you may need to take action.
The Registrant and Eligibility details should look like the following example
Registrant: Trustee of the Example Trust [Details of a Trustee]
Registrant ID: ABN 80000000033 [ABN of the trustee]
Eligibility Type: Trust
Eligibility ID: ABN 80000000001 [ABN of the trust]
Why Now?
This rule isn’t entirely new — the Trustee has always been the eligible party. But until recently, registrars were allowed to assume that a Trust’s ABN referred to a Trustee.
Now, auDA is enforcing a stricter policy:
Registrars must display and validate the Trustee’s ABN/ACN when registering or renewing a domain name.
Different registrars are rolling out this change at their own pace, which is why not everyone has been affected at the same time.
What Do I Need To Do?
If your domain is registered under a Trust ABN that isn’t clearly linked to a Trustee, you’ll need to perform a Change of Registrant (CoR) to update the eligibility information.
This is a common process, usually used when transferring domain ownership during a business sale — but here it’s just being used to correct the ABN on record.
⚠️ Note: The CoR process involves registrar fees and a few approval steps.
How to Complete a Change of Registrant (CoR)
If CommandHost manages your domain, we’ll guide you through the process step by step.
1. Contact CommandHost
Email us at [email protected] or reach out to your account manager to get started.
2. Current Registrant Approves the Process
The current contact will receive an email asking to nominate the "New Registrant" — this is often still you, but with updated ABN details.
3. New Registrant Enters New ABN Details
You'll receive a link to:
-
Enter the correct Trustee ABN/ACN
-
Update contact details
-
Agree to auDA’s terms and policies
4. Final Confirmation from Current Registrant
You’ll be asked one final time to approve the transfer.
5. Verification & Completion
The Registrar verifies the new details, usually within 24–48 hours. Once approved, both the current and new registrants receive confirmation.
Stay Compliant and Hassle-Free
If your domain uses a Trust ABN, now’s the time to act to ensure compliance and avoid service disruption.
If you're unsure about your domain's current status or have questions, we’re here to help.
Contact us: [email protected]
