A subdomain redirect sends anyone who types or clicks a short web address through to a different destination, whether that’s your main website, an online store, a booking page, or a social profile. For a New Zealand business, this usually means turning a memorable name into a working link without touching your main site’s structure. Get the setup right and you can print a link on a sign, a menu, or a business card once, then change where it points as often as your business needs.
This guide separates two things people often confuse: pointing a subdomain at an address using DNS, and actually redirecting a visitor’s browser to a new destination URL. Understanding that difference saves hours of troubleshooting when a link “resolves” but never lands anywhere useful. Registry works in this exact space, offering ready-made r.nz subdomains with editable destinations, so a link on a signboard or QR code keeps working even when what’s behind it changes. If you’d rather skip the DNS admin altogether, the domain-name search is a quick way to see what’s available.
Understanding Subdomains and Forwarding
A subdomain is a named section that sits in front of your main domain, and forwarding is the mechanism that sends a visitor from that address on to somewhere else. The two work together: the subdomain gives you a short, readable name, while forwarding decides what a visitor actually sees when they arrive.
What Is a Subdomain?
A subdomain is a prefix added before your root domain, such as store.example.com or blog.example.com, with example.com acting as the apex or root domain. The www in www.example.com is itself a subdomain, historically used to separate the web-facing part of a domain from other services like mail. Each subdomain can be configured to show different content or point to a different destination entirely, independent of what the main domain does.
What Happens When a Visitor Opens a Redirected Address?
A visitor’s browser looks up the subdomain, connects to whatever server answers for it, and that server issues an instruction sending the browser on to the destination URL. This is domain redirection in practice: the source URL stays visible in marketing material while the actual content lives elsewhere. Nothing about the printed or shared link needs to change when the destination does.
Common Business Uses for Short, Purpose-Led Links
New Zealand businesses often run several destinations off one recognisable name. A cafe might use a base subdomain for its website, then extend it with paths for different jobs: cafe.r.nz/deals, cafe.r.nz/menu, and cafe.r.nz/facebook all sit under one name but each does a different job.
Trades, real estate agents, and consultants use the same pattern for quote forms, open home listings, and booking pages.
Redirecting a Subdomain vs. Pointing It to a Website
Pointing a subdomain at a website using an A record or CNAME record makes it load that server’s content directly, at the same address. Redirecting it sends the visitor’s browser on to a different destination URL entirely, changing what appears in the address bar. Businesses that expect to move destinations often, such as swapping a landing page for a seasonal offer, get more flexibility from a proper redirect than from a static DNS pointer.
How a Redirect Works Behind the Scenes
A redirect only fires after two separate jobs are done correctly: DNS finding the right server, and that server issuing a valid HTTP or HTTPS instruction. Skipping either step is the most common reason a subdomain redirect fails or shows a browser security warning instead of the destination.
DNS Resolves Names but Does Not Send Visitors to a Web Page
The Domain Name System translates a subdomain into an IP address using DNS records such as A records or CNAME records, held with your DNS provider through nameservers and DNS management tools. DNS on its own cannot send a visitor to a specific web page; it only tells the browser which server to contact. Getting a subdomain to actually redirect requires that server, once contacted, to issue an instruction back to the browser.
Why HTTP Status Codes Control the Redirect
The server response includes an HTTP status code that tells the browser what to do next, and that code is what makes a redirect happen. A 301 status code tells browsers and search engines the move is permanent; other codes signal a temporary change. Redirect rules defined on the server or through a redirect service apply this logic automatically whenever the subdomain is requested.
Why HTTPS Needs a Valid Certificate Before Redirecting
If a subdomain is served over HTTPS, it needs its own valid SSL certificate before the redirect instruction can be delivered. Without one, visitors see a browser security warning instead of reaching the destination, no matter how correctly the DNS settings and redirect rule are configured. This is one of the most common points of failure in DIY subdomain redirects, and it’s why services that provision SSL certificates automatically save real setup time.
How Paths and Query Parameters Can Be Preserved
A well-built redirect rule can carry the original path and any tracking parameters through to the destination, so a link like cafe.r.nz/menu lands on the correct page rather than a generic homepage. This matters for campaign tracking, where UTM parameters and campaign IDs need to survive the redirect intact. Preserving this detail is a configuration choice, not something that happens automatically with every setup method.
Which Setup Method Suits Your Business?
The right method depends on how much technical control you want versus how quickly you need a working link. Domain registrars, Cloudflare, cPanel, and raw server configuration all achieve a subdomain redirect, but they differ sharply in setup time, ongoing maintenance, and how SSL certificates get handled.
Using Your Registrar’s URL Forwarding Tools
Registrars such as Namecheap and GoDaddy offer built-in URL redirect records, usually found under advanced DNS settings. You enter the subdomain and the destination URL, and the registrar’s own infrastructure handles the forward. It’s a reasonable option for a simple, rarely-changed redirect, though SSL handling and propagation speed vary by provider.
Creating Redirect Rules in Cloudflare
Cloudflare handles subdomain redirects through redirect rules (formerly page rules) combined with a proxied DNS record, typically an A record pointed at a placeholder IP address. This gives fine control over status codes, path matching, and query string handling, but the subdomain must be proxied through Cloudflare first. It suits businesses already using Cloudflare for their main domain.
Managing Redirects in cPanel or on Your Hosting Server
Most hosting accounts include a Redirects tool in cPanel, under the Domains section, where you choose the subdomain, select a 301 or 302 status, and set the destination. This is a straightforward option if your hosting provider already manages the subdomain’s DNS. It ties the redirect to that hosting account, so moving providers later means reconfiguring it.
Using Apache or Nginx Configuration for Advanced Control
On Apache, .htaccess files use RewriteEngine, RewriteCond, and RewriteRule directives to define custom redirect logic; Nginx uses its own configuration syntax for the same purpose. This method gives the most granular control over conditions and destinations, but a misconfigured rule can take a site offline until it’s fixed. It suits developers comfortable editing server files directly, not business owners wanting a quick change.
When a Managed Branded Link Is the Simpler Choice
A managed service such as Registry removes the DNS record, SSL certificate, and server file entirely from the equation. You choose an available r.nz name through the domain-name search, set the destination from a dashboard, and the redirect is live with SSL security and edge routing already handled. This suits business owners who want a link they can update themselves without calling a developer every time an offer or listing changes.
How to Choose, Test, and Maintain Redirect Rules
Choosing the right redirect type and checking it properly before sharing a link prevents the two most common problems: broken destinations and diluted SEO value. A little diligence here saves reprinting signage or reissuing QR codes later.
When to Use a 301 Permanent Redirect or a Temporary Redirect
A 301 permanent redirect tells browsers and search engines the destination has moved for good, and it’s the right choice for a rebrand, a merged site, or a subdomain that will always point to the same place going forward. A temporary redirect suits short campaigns, seasonal offers, or A/B tests where the original destination will return. Choosing the wrong one can leave search engines indexing the old address long after it stops being useful.
How to Avoid Redirect Chains, Loops, and Conflicting DNS Records
A redirect chain happens when one redirect points to another redirect, which points to another, slowing the visitor down and confusing search engines. A loop happens when two rules point back at each other, which stops the page loading entirely. Keeping DNS records tidy and pointing each redirect directly at its final destination avoids both problems.
Wildcard Redirects and When They Create Risk
A wildcard redirect sends every subdomain under a pattern, such as anything before .example.com, to one destination in a single rule. It’s efficient for consolidating many subdomains at once, but it can accidentally catch subdomains you meant to keep separate, so it needs deliberate scoping rather than a blanket setup.
What Redirects Mean for Search Engines and SEO Value
A properly configured 301 redirect consolidates SEO value at the new destination, so backlinks and search rankings built on the old address aren’t wasted. Search engines treat subdomains as distinct from the main domain, which is one reason businesses redirect an old subdomain into their main site when consolidating content.
Testing Both HTTP and HTTPS Before Sharing a Link
Test a redirect on both the http:// and https:// versions of the address before it goes on a sign or into an ad, since a missing SSL certificate on the source only shows up under HTTPS. Clear the browser cache or use a private window, since cached redirects and DNS propagation delays can make a working rule look broken during testing.
A Stable Digital Front Door for Changing Destinations
A subdomain redirect earns its keep when your business changes faster than your printed materials can. Registry’s approach is built around that reality: claim an r.nz name once, then update the destination whenever your website, offer, or listing changes.
Keep Printed and Shared Links Working When Your Website Changes
A link printed on vehicle signage, a menu, or a real estate signboard has to keep working long after the page behind it moves. With an editable destination, the public-facing r.nz address never has to change, even if the underlying site is rebuilt or migrated.
Create Clear Paths for Menus, Bookings, Campaigns, and Social Profiles
One base name can carry several purpose-led paths, echoing the earlier cafe.r.nz/menu and cafe.r.nz/deals pattern. This keeps a single brand name doing multiple jobs across menus, booking pages, and campaign landing pages, instead of juggling several unrelated URLs.
Use Registry r.nz Links Without DNS or Server Configuration
Setting up a redirect through Registry skips DNS records, SSL certificates, and server files entirely. Redirects run on globally distributed edge infrastructure with sub-50ms global latency, include SSL security by default, and carry automated checks for phishing, malware, and compromised destinations, all without forced interstitial ads or injected tracking pixels.
Choose a Memorable Name and Update the Destination Later
Names like go.r.nz, me.r.nz, or menu.r.nz work because they’re short enough to say out loud and easy to print small. Once claimed, the destination can be changed from the dashboard as often as the business needs, without reissuing a single QR code.
Choose the Redirect Approach That Keeps Links Useful
A subdomain redirect is worth setting up whenever a business needs a short, stable link that can outlast changes to the destination behind it. DNS management, server-side redirect rules, and platform-specific tools like .htaccess or Cloudflare all get the job done for teams with the technical resources to maintain them. For everyone else, a managed branded r.nz link achieves the same result, a working domain redirect with url forwarding built in, without the ongoing DNS management overhead. The right choice comes down to how often the destination will change and who’s available to make that change when it does.
Frequently Asked Questions
Can I redirect a subdomain to a different website?
Yes, a subdomain can redirect to any destination URL, including a completely different website, a specific page, or a social profile. The subdomain’s owner controls the destination, and it can be changed at any time without affecting the public-facing address.
Can a CNAME record redirect visitors to a full URL?
No, a CNAME record only maps one hostname to another hostname at the DNS level; it cannot send a visitor to a specific page or URL. Reaching a particular destination URL requires a server or service that issues an actual HTTP redirect once DNS resolution completes.
Should I use a 301 or 302 redirect for a subdomain?
Use a 301 permanent redirect when the destination is a lasting change, such as a rebrand or site migration, since it consolidates SEO signals at the new address. Use a temporary redirect for short campaigns or seasonal pages where the original destination will return.
Does a redirected subdomain need an SSL certificate?
Yes, if the subdomain is accessed over HTTPS, it needs a valid SSL certificate before the redirect can fire, otherwise visitors see a browser security warning. This applies regardless of which setup method is used, from DNS providers through to server configuration.
How long does a subdomain redirect take to start working?
DNS propagation for a new Registry name takes a few seconds. Once DNS has propagated, the redirect itself takes effect immediately for new visitors.
Can I change the destination without changing a QR code or printed link?
Yes, this is the main advantage of a subdomain redirect over printing a full destination URL directly. As long as the public-facing subdomain stays the same, the destination behind it can be updated as often as needed without reprinting signage or reissuing a QR code.
