DNS finds a destination; it does not choose a page

A URL contains more than a domain name. In https://example.com/old-page, the browser uses the domain name to find where to connect, while the scheme, https, describes how to connect and /old-page identifies a path to request. DNS helps with the domain-name part. It does not receive the full URL from the browser or decide which page should open.

An A record points a name to an IPv4 address, and an AAAA record points it to an IPv6 address. A CNAME record makes one DNS name an alias of another DNS name. None of these records tells a browser to replace https://example.com/old-page with https://example.com/new-page. DNS has no place in those records to specify a replacement path, query string, or protocol.

Why a CNAME is not a redirect

Suppose www.example.com has a CNAME pointing to site.example.net. The browser can use that answer to locate a server, but it still requests www.example.com as the site it wants to visit. The address bar does not change merely because DNS returned an alias. If you want visitors to see site.example.net in the address bar instead, a service handling the web request must send a redirect.

Pointing two names to the same server has a similar limitation. The server may host different websites for those names, so a working DNS answer alone does not guarantee that either name displays the intended site. DNS configuration and web-server configuration must agree.

A redirect happens after the connection

A web redirect is an HTTP response. After the browser reaches a server and requests a URL, that server can respond with a redirect status and a Location header containing the new URL. The browser can then make another request to that address. This is how a request for https://example.com/old-page can lead to https://example.com/new-page.

Permanent redirects, commonly using status 301 or 308, generally suit moves intended to last. Temporary redirects, commonly using 302 or 307, generally suit changes you expect to reverse. The choice can affect how browsers and other clients handle future requests, so select it based on the purpose of the move rather than using whichever option appears first in a control panel.

Where to set up the redirect

If you control the website, you can usually configure redirects in its web server, application, hosting dashboard, or content delivery service. For a single moved page, a rule can map its old path to the new one. For a domain move, rules can cover the old domain and, where appropriate, preserve each requested path. Check how the tool handles query strings if those matter to your site.

Some registrars offer a feature called domain forwarding. Despite appearing next to DNS settings, this is typically a web service that receives visitors’ requests and issues redirects; it is not a special ability of an A or CNAME record. To use forwarding, you may need to point the domain at the provider’s service and configure the destination separately.

For HTTPS visits, the old hostname also needs a working connection and suitable certificate before a browser can receive its redirect response. This matters when retiring a website: removing its hosting or HTTPS setup too early can leave visitors with a connection or certificate error instead of a redirect.

A practical way to check the result

First, decide whether you want an alias or a visible move. If the browser should keep showing the original hostname while loading a site, check DNS and hosting configuration. If the browser should show a new URL, configure a redirect on a service that can answer web requests.

Then test the exact URLs people might use: the root domain, the www name, HTTP if it is supported, HTTPS, and any important old paths. Confirm that the final address is correct and that a request does not bounce repeatedly between two URLs. DNS changes may take time to be seen everywhere because earlier answers can remain cached, but waiting for a DNS change will not turn a record into a redirect. If DNS resolves correctly yet the address bar never changes, look at the web or forwarding configuration next.

Back to category ↗