A client messages their web developer in a panic. They’ve just checked their old domain on a DNS propagation checker and the results look wrong. “I set up forwarding,” they say. “It’s all forwarded. Why isn’t it working?”
The developer asks: “But what will people see when they type in the old URL?”
Silence. Then: “I don’t understand. It’s all forwarded.”
This is one of the most common misunderstandings in web hosting. Domain forwarding sounds like it should be simple — and the person setting it up genuinely believes they’ve done the right thing. But “forwarding” means different things depending on where you set it up, how it’s configured, and what you’re actually trying to achieve.
What Domain Forwarding Actually Does
When you set up domain forwarding through your domain registrar, you’re telling the registrar: “When someone visits this domain, send them somewhere else.”
That’s it. The registrar redirects the browser to a different URL. Your old domain doesn’t serve any content — it just bounces visitors to the new address.
This works, in the narrowest sense. But it introduces problems that aren’t obvious until you check.
The Problems Nobody Mentions
The URL Changes in the Browser
With a standard forward (a 301 or 302 redirect), the visitor’s browser bar changes to the destination URL. If someone types oldname.co.nz, they’ll briefly see that domain, then the browser bar switches to newname.co.nz.
For a rebrand, that might be exactly what you want. But if you’re trying to keep both domains active and make them look like the same site, forwarding doesn’t do that. Visitors will always see the destination domain.
Forwarding Doesn’t Handle Subpages
Most registrar-level forwards send everything to the root of the destination domain. If someone has bookmarked oldname.co.nz/pricing, the forward sends them to newname.co.nz — not newname.co.nz/pricing.
Every deep link, every bookmarked page, every indexed URL in Google — they all land on the homepage. For a site with dozens or hundreds of pages, that’s a serious problem.
Email Doesn’t Forward With the Domain
Domain forwarding only affects web traffic. If you had email addresses on the old domain (info@oldname.co.nz), those stop working entirely unless the MX records are separately configured. Forwarding the domain doesn’t forward the email.
This catches people out regularly. The website seems fine, but a week later someone realises they haven’t received any emails to the old address.
SEO Takes a Hit
Google treats a registrar-level forward differently from a properly configured server-side redirect. Without the correct redirect type (301 permanent) applied at the page level, search engines may not transfer the old domain’s ranking authority to the new one.
Worse, if the forward is a 302 (temporary), Google may keep trying to index the old domain, creating confusion about which site is the “real” one.
What People Think They’re Setting Up vs What They Actually Get
The confusion usually looks like this:
What they expect: Both domains work. Visitors can type either one and see the website. Everything looks professional and seamless.
What they get: One domain redirects to the other. The URL visibly changes. Subpages don’t carry across. Email on the old domain breaks. Google gets confused.
The gap between expectation and reality is where the panicked messages come from.
What Should Happen Instead
If you want two domains to serve the same website properly, the setup needs to happen at the hosting level, not the registrar level:
- Add the second domain as an alias on the hosting server, so both domains resolve to the same site.
- Choose a primary domain and set up proper 301 redirects from the secondary domain to the primary, preserving the full URL path.
- Configure DNS records for both domains — A records, CNAME records, and any necessary TXT records for verification.
- Handle email separately — set up MX records, forwarding rules, or migration depending on what’s needed.
- Set the canonical URL in WordPress or your CMS so search engines know which domain is authoritative.
This is a hosting task, not a registrar task. And it’s the difference between “forwarding” and properly managing multiple domains.
The DNS Propagation Checker Trap
There’s a secondary issue that compounds the confusion: DNS propagation checkers.
These tools — like whatsmydns.com — show you how DNS records are resolving around the world. They’re useful for verifying that a DNS change has taken effect. But they’re also a source of anxiety.
When someone sets up forwarding and then checks a propagation tool, they often see results they don’t understand. The old domain might show a different IP address, or no records at all, or records that don’t match what they expected. Without context, it looks like something is broken.
In reality, what they’re seeing is often correct — the forwarding is doing exactly what it was configured to do. The problem is that what it was configured to do isn’t what they needed.
When Forwarding Is the Right Choice
Domain forwarding isn’t always wrong. It’s appropriate when:
- You’ve permanently moved to a new domain and the old one exists solely to catch stragglers.
- You own common misspellings of your domain and want them to redirect to the correct one.
- You’ve registered a
.comto complement your.co.nzand just need a simple redirect.
In these cases, a clean 301 forward at the registrar level is simple and effective. The key is understanding that it’s a redirect, not a mirror.
The Takeaway
“I set up forwarding” is one of those phrases that sounds definitive but tells you almost nothing. The person saying it believes the job is done. The person hearing it knows the job might not have started.
If you’re managing your own domains and something isn’t working the way you expected, the first question to ask isn’t “is it propagated?” — it’s “what exactly did I set up, and is that actually what I need?”
And if the answer to that second question isn’t immediately clear, that’s exactly when it’s worth talking to your hosting provider.
