DNS vs URL redirects: when to use A, CNAME or 301

DNS helps a browser find a server. An HTTP redirect tells the browser to request another URL. They operate at different stages of a visit. Pointing one domain's CNAME at another generally does not change the address bar to that destination, and it does not automatically migrate individual page paths.

Define what the visitor should experience

Write a testable goal before editing settings. For example: visiting www.example.com should show example.com in the address bar while retaining the requested article. A change involving the address bar or page path usually needs more than DNS.

Why DNS cannot select a page path

DNS queries concern hostnames, not whether a visitor requested /pricing/ or /blog/. A and AAAA return IP addresses; CNAME creates an alias relationship. Do not paste a complete URL containing a scheme or path into these fields. Some hosting products create records and certificates automatically, but their hostname and path behavior still needs checking.

When connecting shop.example.com to a project, bind that exact hostname at the host before applying its supplied records. Two hostnames returning the same IP do not necessarily serve the same project. One server can host many websites, with the requested hostname determining which one is shown.

Redirects and canonical URLs serve different purposes

A permanent move normally needs a permanent server redirect; a temporary campaign may need a temporary redirect. Choose a status code matching the actual intent. Google treats permanent redirects as an important signal for the target URL. A canonical reference is a signal about the primary version; it does not move a visitor's browser and cannot replace a redirect that must actually occur.

Avoid sending every unrelated old page to the homepage. Map old URLs to relevant replacements. Decide separately what to do when no replacement content exists rather than disguising that absence as a working new article.

Test the full request chain

• Check DNS and a valid HTTPS connection for the source address.
• Inspect the source response status and redirect target.
• Verify that the destination returns the intended page and does not redirect back.
• Test page paths and necessary query parameters, not just the homepage.
• Update internal links and the sitemap to reference the final URL directly.

A correct address bar is only one check. Verify images, buttons, forms and language switching too. Preserve the previous configuration and a rollback approach. Troubleshoot DNS, host binding, certificates, redirects and application behavior as separate layers.