How to Set Up Domain Forwarding Correctly
A domain name can remain useful long after a website changes platform, ownership or purpose. Forwarding gives visitors a dependable route from an old address to a current one, helping preserve recognition, search visibility and links shared in earlier years. It is especially valuable for a resource hub that brings together archived news, community writing and historical sections.
The basic idea is simple: someone enters one domain, and their browser is sent to another web address. Correct implementation requires more than entering a destination into a registrar dashboard. You need to choose the right redirect, protect email services, account for HTTPS, and test common versions of the domain.
Australian website owners may be working with a local .com.au or .au address, an international domain, or several names acquired for a community project. A business in Melbourne might redirect an older campaign domain to its main site, while an organisation in Brisbane could preserve an archive under a new hosting account. Each situation needs a clear record of what should happen.
Good forwarding also supports long-term digital stewardship. Historical pages should remain easy to find, old printed material should continue to work, and visitors should not be trapped in a chain of expired links. The goal is a stable path that serves both people and search engines.
Why Forwarding Needs A Clear Plan
Start by writing down every domain and subdomain involved. Include the preferred address, common variations such as www, and any country-code domains. Decide whether visitors should land on the homepage, a matching section or a specific replacement page. Sending every old URL to a generic homepage can confuse visitors and may weaken the value of established links.
A forwarding plan is particularly important when preserving community material. An old address might point to a local story, event notice or family-history page that has a clear equivalent on the new site. For example, a preserved article collection such as community history should be reached through a meaningful destination rather than an unrelated front page.
Record the current registrar, hosting provider, DNS provider, renewal date and administrative contact. These services may be controlled by different companies. A domain can be registered with one provider, use DNS hosted by another, and have its website stored somewhere else. Confusing these roles is a common reason forwarding changes appear not to work.
Check ownership and access before making changes. For .au domains, eligibility and registrant details are governed through the .au domain administration framework, and inaccurate records can create renewal or transfer problems. Keep invoices, authorisation codes and account recovery details in an organised location, especially if the domain supports an archive that needs care over many years.
Choose The Right Redirect Method
A server-side 301 redirect is generally the best choice when a domain or page has moved permanently. It tells browsers and search engines that the old address has been replaced. A 308 redirect also indicates a permanent move, although 301 remains more widely supported in ordinary website management tools.
Use a 302 or 307 redirect when the change is temporary, such as during a short campaign, maintenance period or controlled test. A temporary redirect signals that the original address may return. Choosing a temporary status for a permanent migration can delay the transfer of search signals and create uncertainty for visitors.
Registrar forwarding is convenient when the old domain does not need its own hosting account. It usually sends the browser to the new address, often through a provider-managed service. Ask whether the service supports HTTPS, path preservation and permanent status codes. Some basic plans forward only the bare domain and lose the rest of the URL.
Avoid masked or framed forwarding for a normal website migration. This approach can keep the old address in the browser bar while displaying the new website inside a frame. It may interfere with analytics, accessibility, browser security, sharing and search indexing. A visible, direct redirect is clearer and easier to maintain.
Protect DNS, Email And HTTPS
DNS forwarding is frequently confused with web redirection. DNS translates a domain into a server address; it does not, by itself, tell a browser to move from one URL to another. A hosting server, CDN or registrar forwarding service must deliver the HTTP redirect response.
Keep required DNS records before changing nameservers. Mail exchange records, or MX records, control where email is delivered. TXT records may support SPF, DKIM, DMARC, domain verification or other services. Replacing the full DNS zone with a simplified forwarding setup can interrupt mailboxes used by staff, volunteers or local suppliers.
If email is attached to the old domain, decide whether it should continue. A domain used for correspondence may need separate mail hosting even when its website is forwarded elsewhere. Test sending and receiving from real accounts, including addresses such as info@, before announcing the change. Website redirection does not automatically redirect email.
HTTPS needs its own check. Visitors may type https://old-domain.au, and modern browsers expect a valid certificate before they accept the redirect. Some registrar forwarding products provide certificates automatically; others require the domain to be connected to a hosting platform or CDN. Confirm that both the bare domain and www version work securely.
DNS changes can take minutes, several hours or, in some cases, longer depending on TTL values and cached records. Australian organisations operating across Sydney, Perth and regional areas may see inconsistent results while providers refresh their systems. Test using mobile data as well as a home NBN connection, since different networks can hold cached information for different periods.
Test The Visitor Journey
Test each variation in a private browser window: the bare domain, the www version, HTTP, HTTPS, a known old page and a destination with a path. Check whether each one reaches the intended page in a single hop. A redirect chain such as old domain to an intermediate domain and then to the final site is slower and more likely to break.
Review the browser address bar after the page loads. The destination should be visible, and the connection should show as secure. Use a redirect-checking tool or browser developer tools to confirm the status code. A permanent migration should normally return 301 or 308, while a deliberately temporary arrangement should use 302 or 307.
Check mobile presentation because many Australians access services on phones during commuting, school pickup or travel between suburbs. A redirect that works on a desktop may still lead to an oversized page, an incompatible path or a blocked security resource on mobile. Test common browsers and at least one device connected through a different network.
Search engines need consistent signals. Update internal links, XML sitemaps, canonical tags and online business profiles. If the old site had valuable pages, map each significant URL to its closest equivalent. Keep the old domain registered and forwarding for as long as practical, since printed brochures, social posts, news stories and community directories can remain active for years.
For an Australian business, also review references in Google Business Profile, local directories and supplier portals. A Sydney café, Melbourne tradesperson or Adelaide community group may have its domain printed on signs and invoices. Correcting those references gradually reduces reliance on the redirect while protecting visitors who still use older material.
Maintain A Reliable Forwarding Setup
Forwarding is a maintenance responsibility rather than a one-off switch. Set calendar reminders for domain renewal, hosting renewal and certificate expiry. A domain that expires can be registered by someone else, leaving old links broken or exposing visitors to an unrelated website. Use auto-renewal where appropriate, but retain payment and account recovery controls.
Monitor traffic and error reports after launch. A sudden rise in 404 errors may indicate that paths were not preserved. Repeated requests for an old page can show where a specific redirect is needed. Analytics should distinguish referral traffic from the old domain so that the value of historical links can be understood.
The following approaches suit different levels of control and different migration goals:
| Forwarding approach | Best use | Main strength | Key limitation |
|---|---|---|---|
| Registrar URL forwarding | Simple domain-to-domain move | Quick setup with little hosting work | May have limited HTTPS, path and status-code control |
| Server-side 301 redirect | Permanent website or domain migration | Strong control over paths and search signals | Requires hosting or server access |
| CDN or edge redirect | High-traffic or multi-domain projects | Fast global handling and flexible rules | More technical configuration |
| Temporary 302 or 307 redirect | Testing, campaigns or short maintenance | Keeps the original move reversible | Unsuitable for a permanent relocation |
| Masked forwarding | Rare legacy display requirement | Keeps an old address visible | Can harm usability, security and indexing |
Before publishing the new address, confirm that the redirect has a single destination, email records remain intact and the old domain will be renewed. Keep a short change log with the date, provider, settings and test results. That record helps a future administrator understand why the forwarding exists and how to restore it.
Recommended Checks Before Launch
- Choose a permanent 301 or 308 redirect when the move is intended to last.
- Test bare,
www, HTTP, HTTPS and important old page URLs. - Preserve MX, SPF, DKIM, DMARC and other DNS records needed for email.
- Keep both domains registered and renew them before the expiry date.
- Review analytics, search-console reports and broken links after the change.
A careful setup makes an old address useful instead of treating it as disposable. For domain owners, archive managers and community organisations, that continuity protects years of printed references, search results and shared knowledge. Put the forwarding rules, renewal dates and destination mapping into a written record, then review them whenever the website structure changes.
If a domain is being transferred, retired or connected to preserved materials, establish the redirect before publicising the new location. Visitors should arrive at the right page without seeing confusing warnings, unexpected frames or dead ends. A stable forwarding arrangement keeps the domain’s history connected to its present purpose and gives future readers a reliable way to access the site.