Domain forwarding looks simple, but the best setup depends on whether you need DNS resolution, a web-server redirect, or a managed URL redirect service. This guide explains the difference, shows how to redirect a domain securely over HTTPS, and provides reusable checklists for parked domains, domain changes, vanity URLs, campaigns, and site migrations.
Overview
A domain redirect sends visitors from one hostname or URL to another. For example, old-example.com might send visitors to new-example.com, while example.com/sale might forward to a specific campaign landing page.
The important distinction is that DNS does not usually perform the redirect itself. DNS tells a browser or other client where a domain’s service can be found. The redirect response is normally generated by a registrar’s forwarding service, a web server, a CDN, or a redirect management platform after the request reaches that service.
| Option | What it does | Best suited to | Key limitation |
|---|---|---|---|
| DNS records | Point a hostname to an IP address, hostname, or hosted service | Connecting a domain to hosting, email, or a proxy | DNS alone does not provide a normal HTTP 301 or 302 redirect |
| Registrar forwarding | Accepts a domain request and sends visitors to another URL | Parked domains, simple domain forwarding, and basic aliases | Features, HTTPS handling, paths, and query-string behavior vary by provider |
| Web-server redirect | Returns an HTTP redirect from Apache, Nginx, a host, or an application | Domain changes, URL migrations, and rules tied to site infrastructure | Requires access to the hosting or server configuration |
| Managed redirect service | Applies centralized rules, tracking, and routing before sending visitors onward | Campaign links, branded short links, QR codes, geo or device rules, and teams | Requires maintaining the service configuration and domain connection |
Choose a permanent 301 redirect when the source URL has moved and you expect the change to remain. A 302 or another temporary redirect is more appropriate when the destination may change back or the routing is being tested. For a broader explanation of status codes, see the HTTP Redirect Status Codes Cheat Sheet.
Checklist by scenario
For a parked or alternate domain
- Decide whether the alternate domain should resolve to the homepage or to a specific path.
- Confirm that you control the domain’s registrar account and can edit its nameservers or DNS records.
- Choose registrar forwarding, hosting, or a redirect management platform based on whether you need analytics, multiple rules, or future flexibility.
- Configure both the root domain and the
wwwhostname if both should work. - Test HTTP and HTTPS versions, including the final destination and any trailing-slash behavior.
For a domain change or rebrand
- Inventory important URLs on the old domain, not only the homepage.
- Map each old URL to the closest relevant URL on the new domain. Avoid sending every page to the homepage when a more specific destination exists.
- Implement server-side permanent redirects where possible.
- Update canonical URLs, internal links, XML sitemaps, analytics settings, email templates, ads, social profiles, and important third-party listings.
- Monitor logs and analytics for requests to old URLs, redirect errors, chains, and unexpected destinations.
For a larger migration, use the 301 Redirect Mapping Template or the bulk URL redirects migration checklist to organize source URLs, target URLs, status codes, owners, and verification results.
For a vanity URL, campaign, or affiliate link
- Use a memorable source path, such as
brand.example/spring, rather than exposing a long destination URL. - Build the final destination with consistent UTM parameters before creating the redirect.
- Preserve necessary query parameters unless there is a deliberate reason to replace them.
- Use a managed redirect platform when the destination, campaign owner, or reporting requirements may change.
- Record the redirect name, purpose, destination, launch date, and owner in a shared naming system.
The UTM Link Management Guide covers a repeatable approach to campaign parameters. For printed materials or permanent signage, consider a dynamic QR code redirect so the destination can be updated without replacing the code. See the dynamic QR code redirect guide.
For a simple DNS and hosting connection
- Identify whether the host requires an A record, AAAA record, CNAME, or nameserver delegation.
- Remove conflicting records only after confirming what other services use the domain.
- Keep email records, verification records, and subdomains intact unless they are intentionally being migrated.
- Allow for DNS caching while testing, but do not treat DNS propagation as proof that the HTTP redirect is correct.
- Once the hostname reaches the intended server, configure the redirect at the hosting, CDN, or web-server layer.
What to double-check
DNS configuration
- Check the authoritative nameservers first; editing records at the wrong DNS provider will have no effect.
- Confirm that the root domain and
wwware handled separately where required. - Look for conflicting A, AAAA, CNAME, or forwarding records.
- Review the TTL before a planned migration, while remembering that recursive resolvers may retain cached data.
- Protect unrelated records used for email, domain verification, subdomains, and other services.
TLS and HTTPS
HTTPS forwarding requires more than a redirect rule. The source hostname must first complete a TLS connection, so the service receiving the request needs a valid certificate for every hostname visitors may enter. Check the apex domain, www, common subdomains, and any alternate domain in the redirect.
- Confirm that the certificate covers the requested hostname.
- Test
http://andhttps://source URLs independently. - Check whether HTTP redirects to HTTPS before the domain redirect, or whether the service handles both directly.
- Renew certificates before their validity period ends and document who owns renewal access.
- Verify that the final destination also uses HTTPS and does not create a redirect loop.
Redirect behavior
- Confirm the response status with a redirect checker or command-line request.
- Check whether the path is preserved, replaced, or discarded.
- Check whether query strings, including tracking parameters, are preserved.
- Look for chains such as old domain to HTTP new domain to HTTPS new domain. A direct final redirect is usually easier to test and maintain.
- Make sure the destination does not point back to the source.
Useful verification commands include:
curl -I https://old-example.com/pathTo follow the complete route and inspect each response, use:
curl -IL https://old-example.com/pathTo inspect DNS resolution, use commands supported by your operating system, such as:
dig old-example.com A
dig www.old-example.com CNAMECompare the returned status, Location header, certificate hostname, and final URL with the intended configuration. If you find multiple hops or a loop, use the redirect chain and loop checker workflow.
Common mistakes
- Confusing DNS with forwarding: An A or CNAME record connects a hostname to infrastructure; it does not automatically tell a browser to navigate to a different URL.
- Redirecting only one hostname: A setup for the apex domain may not cover
www, and vice versa. - Forgetting HTTPS on the source: Visitors may enter an HTTPS URL directly, so the source service must be able to complete TLS before returning a redirect.
- Using a temporary redirect for a permanent move: Select the status code based on the intended lifetime of the change, not on which option is easiest to find in an interface.
- Dropping campaign parameters: Test query-string handling when attribution matters. The guide on preserving tracking parameters across redirects provides a focused checklist.
- Creating redirect chains: Point the old URL directly to the final canonical destination whenever practical.
- Sending every old page to the homepage: Use page-level mappings for migrations so visitors and crawlers reach the most relevant replacement.
- Leaving undocumented rules: A redirect without an owner, purpose, or review date becomes difficult to change safely.
- Testing only in one browser: Check status codes and headers directly, then test representative URLs from different networks or devices where the campaign warrants it.
When to revisit
Treat domain forwarding as an operational asset, not a one-time setting. Revisit the configuration before seasonal planning cycles, major campaigns, domain renewals, hosting changes, certificate renewals, rebrands, and website migrations. Review it whenever a registrar, DNS provider, CDN, hosting platform, or redirect management workflow changes.
At each review, confirm the domain owner and billing contact, nameservers, DNS records, TLS coverage, redirect status codes, destination URLs, query-string behavior, analytics data, and expiration or renewal dates. Sample important links with curl -IL, inspect redirect analytics for unexpected spikes or dead destinations, and remove obsolete rules only after checking their traffic and dependencies.
Keep a dated change record containing the source, destination, status code, rule owner, reason for change, and verification result. For large URL sets, maintain the mapping in a shared spreadsheet or redirect platform and run a bulk check after every migration. This turns domain forwarding from a fragile collection of settings into a documented system that can be reviewed whenever the underlying domains, hosts, certificates, or workflows change.
Final action: Before publishing a redirect, write down the exact source URL, final destination, intended status code, HTTPS requirement, parameter behavior, and rollback plan. Then test the source with and without www, over HTTP and HTTPS, with a representative path and query string. That short checklist catches most configuration errors before visitors do.