Domain forwarding and server-side URL redirects can both send visitors from one address to another, but they are not interchangeable. This guide explains the setup, DNS, HTTPS, path, query-string, SEO, email, and portability differences so you can choose the right method and verify it before launch.
Overview
Domain forwarding is usually a feature provided by a registrar, DNS provider, or hosting company. You enter a source domain and a destination URL, and the provider handles the request. Depending on the provider, forwarding may be implemented through a hosted forwarding service, a web server, or an iframe-style presentation. The exact behavior matters, so review the provider’s settings and test the result rather than assuming every forwarding feature works the same way.
A server-side URL redirect is a response generated by a web server, application, CDN, or redirect management platform. The server returns an HTTP status such as 301 or 302 and a Location header pointing to the destination. This approach gives you more control over individual paths, query strings, rules, headers, logging, and future changes.
DNS is part of the delivery path, but DNS alone does not normally issue an HTTP redirect. An A, AAAA, or CNAME record points a hostname toward infrastructure. That infrastructure must then serve the redirect response. Some DNS providers offer URL forwarding as an additional service; it is more than ordinary DNS resolution.
| Consideration | Domain forwarding | Server-side URL redirect |
|---|---|---|
| DNS | Often configured through a registrar or forwarding provider; implementation varies. | DNS points the hostname to a server, CDN, or redirect platform that returns the response. |
| Hosting | May not require your own web hosting, but depends on the provider’s forwarding service. | Requires access to a web server, application, CDN, or redirect management platform. |
| HTTPS | Requires the forwarding provider to support certificates for the source domain. | You control or delegate certificate coverage for every source hostname. |
| Paths | May forward only the domain, or may preserve paths if the provider supports it. | Can map individual paths, patterns, and legacy URLs precisely. |
| Query strings | Parameter preservation depends on the provider’s forwarding behavior. | Can preserve, remove, or transform parameters deliberately. |
| SEO behavior | Can work for a simple permanent move if it returns the intended status and destination. | Offers clearer control over 301, 302, destination consistency, and migration rules. |
| Email impact | Web forwarding does not automatically forward mail; email DNS records must remain separate. | Web redirect configuration should not replace MX, SPF, DKIM, or other mail records. |
| Portability | Convenient, but behavior and settings can be tied to the provider. | Rules can be exported or recreated, though server and platform dependencies still matter. |
Use simple domain forwarding when the requirement is limited to sending one domain or hostname to another and the provider supports HTTPS and path behavior you can verify. Choose a server-side redirect or redirect management platform when you need a site migration, bulk URL redirects, branded short links, campaign routing, QR code destinations, or rules based on paths, devices, locations, or campaigns. For status-code decisions, see 301 vs 302 Redirects: Which Status Code Should You Use?.
Checklist by scenario
Scenario 1: Forwarding a newly purchased domain
- Confirm the exact source hostnames: the bare domain,
www, or both. - Choose the permanent or temporary behavior that matches your intent. A lasting brand or domain move generally calls for a permanent redirect; a test or short-lived campaign may need temporary behavior.
- Enter the complete destination URL, including the preferred protocol and path.
- Check whether the provider preserves the path and query string. Do not assume that
/offer?utm_source=printwill arrive unchanged. - Enable HTTPS forwarding if available, and confirm that the certificate covers the source hostname.
- Test both HTTP and HTTPS, with and without
www, before publishing the address.
Scenario 2: Redirecting through DNS and your own web server
- Set the required A, AAAA, or CNAME records at the DNS provider. Use the records supplied by your hosting, CDN, or redirect service.
- Allow for DNS changes to become visible according to the relevant DNS caching and TTL behavior.
- Configure the source hostname in the web server or platform.
- Install or enable a certificate for every HTTPS hostname that will receive traffic.
- Add an explicit redirect rule. Decide whether paths and query strings should be retained, mapped, or removed.
- Place the rule before broader application routes where necessary, and test for loops.
Scenario 3: Migrating a website or changing domains
- Export a list of important old URLs, not just the old homepage.
- Create one destination for each meaningful URL, prioritizing an equivalent page rather than sending every request to the homepage.
- Use bulk URL redirects or a redirect management platform when the list is large or needs ongoing ownership.
- Keep the old domain, DNS configuration, and certificates active for as long as the migration plan requires.
- Update internal links, canonical destinations, campaign links, XML sitemaps, and external profiles where you control them.
- Review logs and analytics for missed URLs and unexpected destinations. The guide to redirect chains and loops can help with troubleshooting.
Scenario 4: Marketing, QR codes, or campaign links
Use a redirect platform when the destination may change after printed materials or ads are published. A dynamic QR code redirect can keep the QR code unchanged while the destination is updated. For campaign traffic, establish a consistent UTM convention and verify that parameters survive the redirect; see How to Preserve URL Parameters Through Redirects and UTM Link Governance.
What to double-check
- Status and headers: Use a redirect checker or browser developer tools to confirm the expected 301 or 302 response and the final
Locationheader. Check every hop, not only the final page. - Certificate coverage: Visit each source hostname over HTTPS. A redirect that works over HTTP but produces a certificate warning over HTTPS is not a complete domain redirect.
- Canonical destination: Confirm that the final URL uses the intended protocol, hostname, path, and trailing-slash convention. Avoid sending visitors through several intermediate URLs.
- Paths and parameters: Test the homepage, a deep path, a path with a query string, and a path that should not exist. Confirm whether tracking parameters are preserved without creating duplicate or unsafe destinations.
- Email records: Review MX and related mail records before changing DNS. Web forwarding does not deliver email, and replacing mail records can interrupt legitimate mail flow.
- Rules and fallbacks: If you use device, geographic, affiliate, or campaign rules, define a clear default destination and test unsupported or missing conditions.
- Ownership: Record the registrar, DNS provider, certificate owner, redirect platform, rule purpose, and destination owner. This makes later migrations and incident response safer.
Common mistakes
Confusing DNS with a redirect. Adding a CNAME does not, by itself, tell a browser to move to a different URL. It only helps route the hostname to infrastructure that can respond.
Forgetting HTTPS. A source domain may receive substantial direct traffic over HTTPS. Certificate setup must be part of the redirect plan, not an afterthought.
Forwarding only the homepage. A domain-level rule may not preserve old article, product, or campaign paths. Map important URLs individually during a migration.
Dropping query strings. Removing UTMs or affiliate parameters can make campaign reporting incomplete. Conversely, blindly copying every parameter can create unwanted destinations. Define the rule intentionally.
Creating chains and loops. A source that points to another redirect, which then points to a third URL, adds avoidable complexity. A rule that redirects a destination back to the source can make the page unreachable.
Replacing mail DNS records. Keep web and email requirements separate. Before changing DNS, document records used for mail and other services.
Leaving temporary rules indefinitely. Label campaign and test redirects with an owner, purpose, and review date. For branded links and ownership practices, see Branded Short Links: Naming, Ownership, and Lifecycle Management.
When to revisit
Recheck this setup before a domain purchase, rebrand, site migration, seasonal campaign, QR code print run, subdomain launch, or certificate renewal. Revisit it after changing registrars, DNS providers, hosting, CDNs, redirect platforms, or application routing. Browser behavior and provider interfaces can change, so verify the current controls rather than relying on an old screenshot or remembered workflow.
At minimum, repeat the validation checklist whenever a DNS or hosting change is made: request each source over HTTP and HTTPS, inspect status codes and headers, test representative paths and parameters, confirm the certificate, check the final canonical destination, and verify that email records remain intact. Keep a dated redirect inventory with the rule owner and intended end state. That small maintenance habit helps prevent expired campaign links, broken QR destinations, migration gaps, and unnoticed redirect chains.