What is DNS and how to change it for your domain
The Domain Name System, or DNS, is the internet’s address book: it translates a memorable domain name, such as yourbrand.com.au, into the numerical IP address a browser or mail server needs to connect. A recursive resolver checks its cache and, if necessary, asks the root and .au nameservers before an authoritative server supplies the answer.
Changing a domain’s DNS means changing either its nameservers or the records hosted by its DNS provider. The process can improve performance, support new services or redirect traffic, but incorrect changes may interrupt websites, email and certificates. This guide explains the practical steps for Australian domain owners.
| DNS record | Main purpose | Typical example |
|---|---|---|
| A | Connects a hostname to an IPv4 address | 203.0.113.10 |
| AAAA | Connects a hostname to an IPv6 address | 2001:db8::10 |
| CNAME | Points one hostname to another | www to yourbrand.com.au |
| MX | Directs incoming email to a mail server | mail.yourbrand.com.au |
| TXT | Stores verification and email policy details | SPF, DKIM and DMARC values |
How the domain name system works
DNS operates as a distributed directory. When someone visits your website, their device asks a recursive resolver for the relevant IP address. If the answer is not cached, the resolver follows the hierarchy from the root servers to the .au top-level domain and then to your domain’s authoritative nameserver.
Each answer has a time-to-live, or TTL, value that determines how long a resolver may keep it. A shorter TTL allows changes to spread more quickly, while a longer TTL can reduce lookup traffic. This is why a DNS update may work for one visitor before appearing to fail for another.
The .au namespace is managed by auDA, while .com.au is the commercial branch commonly used by Australian businesses. DNS itself is separate from domain registration and web hosting, so a domain can remain registered with one company while its records and nameservers operate through another.
Find the DNS service controlling your domain
Your domain registrar is usually the company where you purchased or renewed the name. It may provide basic DNS hosting, or it may point the domain to a specialist DNS provider such as Cloudflare, Google, Microsoft or an Australian hosting company. The registrar controls nameserver delegation, while the DNS provider controls the actual records.
Sign in to the registrar and locate the domain’s nameservers or DNS settings. You can also inspect them with dig yourdomain.com.au NS +short or nslookup -type=ns yourdomain.com.au. Write down the current nameservers and every existing record before making a change.
Changing the DNS option on a Telstra, Optus or Aussie Broadband router is a separate operation. It affects DNS lookups for devices connected through that router, not the authoritative settings for your registered domain. Australian registrars often bill renewals in AUD and provide local support, although DNS records can be hosted anywhere.
Back up records before making changes
Create an inventory of your website records, subdomains, mail servers and third-party services. Include the root domain, www, landing pages, analytics hosts, CDN aliases and any abandoned pages. For email, record the MX destinations plus SPF, DKIM and DMARC TXT records.
Lower the TTL on important records to 24 or 48 hours at least a day before the planned update. This gives resolvers time to replace their cached answers with the shorter lifetime. Keep the old values available so the service can be restored if the new configuration is incomplete.
Registration and DNS are different layers of control. Changing nameservers does not transfer a .com.au domain, renew it or alter auDA’s Australian presence requirements. Avoid deleting the domain during the process, and confirm that the registrar still shows it as active until the new DNS configuration is working.
Change nameservers or records safely
To replace nameservers, open the domain management page in your registrar, select the DNS or nameserver option and choose custom nameservers. Enter the exact hostnames supplied by your DNS provider rather than their IP addresses. Most providers require at least two nameservers, then you save and verify the delegation.
Alternatively, keep the current nameservers and edit the records at the existing DNS host. Change an A or AAAA record when moving a hostname to a new server, or use a CNAME when the provider gives you an alias. Retain both an IPv4 and IPv6 route where possible, and confirm that CDN proxy settings match the intended configuration.
After saving, allow the previous TTL period to expire. Changes may become visible within a few hours, although propagation can take up to 48 hours or longer in some locations. Do not remove a DNSSEC digital signature record until the new provider confirms it can validate the domain, as mismatched signing information can prevent resolution.
Check that the change has propagated
Compare the new answer with the authoritative provider. Run dig yourdomain.com.au A +short and dig @1.1.1.1 yourdomain.com.au A +short; the addresses should agree once propagation is complete. For Windows users without dig, nslookup yourdomain.com.au provides a useful alternative. Also check the MX records and send a test email.
A stale local cache can make a completed update appear unsuccessful. Flush the operating system cache, restart the router or test from a mobile network. The same check applies when a redirect points to an external page, such as online casino information, because a stale CNAME can send visitors to the wrong destination.
Test from more than one Australian connection. A resolver used by a Sydney office may retain an old answer while a connection in Perth, Adelaide or Brisbane returns the updated record. If results differ, continue checking the authoritative nameservers rather than repeatedly saving the same configuration.
Secure DNS and prevent takeover risks
Protect the registrar and DNS accounts with multi-factor authentication, strong unique passwords and restricted staff permissions. Remove former employees and contractors promptly. The Australian Cyber Security Centre provides guidance on domain and account compromise that is relevant to Australian businesses managing .com.au websites.
Enable DNSSEC only when the registrar and DNS provider both support the correct signing chain. Keep the domain’s digital signature records and provider configuration aligned, then use the provider’s validation tools to confirm the chain works. For additional protection against accidental exposure, use encrypted DNS such as DNS over HTTPS or DNS over TLS where practical.
Review old TXT records, unused subdomains and dangling CNAME targets periodically. These can be exploited for unwanted mail or domain takeover. Keep automatic renewal active, retain an exported DNS backup and report suspected .au abuse through the registrar or auDA. A short, documented change process is safer than emergency edits made without a record of the previous setup.
Put your DNS change into practice
Begin by identifying whether you need to replace nameservers or simply edit one record. A hosting migration or DNS provider change usually calls for new nameservers, while moving a subdomain or adding a mail route is usually handled through individual records.
Copy the existing configuration, shorten the TTL, apply the change and verify it from several Australian networks. Check the website, HTTPS certificate, redirects, contact forms and both incoming and outgoing email before treating the migration as complete.
Open your registrar dashboard now, export your current DNS settings and schedule the update during a low-traffic period. Keep the backup available until the new records have propagated and every essential service has passed a practical test.