Forward a domain: DNS is not a 301 redirect

Pointing two domains at one server is not the same as redirecting one URL to another. Permanent forwarding normally requires an HTTP redirect service.

DNS locates the service

DNS locates infrastructure. The receiving web service must recognise the source domain, serve HTTPS and return the redirect response.

Preserve relevant paths

During a site move, map old pages to relevant new pages rather than sending every visitor to the homepage. Even a simple brand-domain redirect needs testing.

Test the whole chain

Test protocol and www variants, deep paths and canonical URLs. Avoid unnecessary chains or loops. Our standard DNS controls are not themselves a full HTTP redirect service.

Your practical checklist

• Choose a redirect-capable service.
• Support HTTPS on the source.
• Map important old URLs.
• Check chains and loops.

Sources and further reading

• Google Search Central: site moves

Registration rules and provider functions can change. Check the current requirements for your domain before ordering or changing services.