What DNS actually does
DNS translates a domain name into a server address. When a customer types your address or taps a link in your Instagram bio or a Telegram channel, DNS answers one question: where should the request go? It doesn't decide which page to show or which status code to return.
A redirect is an HTTP response that carries a status code, such as 301 or 302, and a destination address. A web server or proxy sends it. That's why no record in your DNS panel can create a real redirect by itself.
- A and AAAA: point a domain to a server's IPv4 or IPv6 address
- CNAME: makes one hostname an alias of another
- MX: defines where the domain's email is delivered
- TXT: service data, including site verification for Search Console and Google Ads
Why a CNAME is not a redirect
The most common mistake is pointing a CNAME from the secondary domain to the main one and expecting visitors to be forwarded. The browser does reach the right server, but the secondary domain stays in the address bar, and the request carries that name.
Two things can happen next. The server doesn't recognise the name and shows an error or someone else's placeholder page. Or it does recognise it and serves the same site on two addresses, which gives search engines a duplicate and splits your links between domains. Either way, no 301 is ever sent.
Setting up a DNS redirect that actually works
When people say they want a DNS redirect, they usually end up with one of three setups. In each of them DNS just routes traffic to a place that can answer with a redirect.
- Your own hosting or server. Add the secondary domain to the main site's server, point DNS to it with an A record, and write a 301 rule in the server config. The HTTPS certificate is issued there too.
- A proxy service such as Cloudflare. DNS is managed there, traffic passes through its network, and the redirect rule lives in the same place. No hosting is needed for the extra domain.
- A registrar feature. It can be fine for one or two domains, but it needs checking: it isn't DNS, it's the registrar's own web server answering behind your record.
Traps in the registrar's forwarding option
A "forward domain" button is convenient, but the result can surprise you. A typical story: a company turns it on for its .com, and a month later finds that visitors see a certificate warning while search engines treat the jump as temporary.
Before relying on such a feature, check four things:
- Status code: a permanent move needs 301, not 302
- Path: an address ending in /catalog/ should lead to /catalog/, not to the homepage
- HTTPS: the domain must open over a secure connection with no warnings
- Masking: if your site loads inside a frame and the address never changes, it's useless for SEO
Protecting email and rankings during the switch
DNS records are cached, so changes don't reach every user at the same moment. If you plan a switch, lower the TTL of the records beforehand so old values expire from caches sooner.
The second risk is email. When you move DNS management to another service, you have to copy MX and TXT records along with the A records. Otherwise the redirect works but enquiries and Click or Payme notifications stop arriving, and you may not notice for days.
Finally, verify the result by status code, not by the fact that a site opened. Use a header-checking tool and confirm there's a 301, the right destination and a preserved path.
What this means for SEO
A correct 301 passes accumulated link value to the new address and avoids duplicates. A wrong one sends part of your traffic from search, OLX listings or ad links into a dead end. If you are changing a domain or merging several addresses, plan redirects as part of your SEO work, not as a technical footnote.
The markdev team handles this kind of task within SEO optimisation in Uzbekistan: we audit existing redirects, pick a method that fits your infrastructure and support the migration. If you own several domains and aren't sure how search engines treat them, tell us about the task and we'll see where to start.
FAQ
Can I set up a redirect in DNS alone, without hosting?
A DNS record cannot perform a redirect by itself. You don't need hosting for the extra domain, though: a proxy service with redirect rules, or a registrar feature that returns 301, supports HTTPS and keeps the path, can do the job.
What is the difference between a CNAME and a redirect?
A CNAME only makes one hostname an alias of another at the DNS level. The browser address doesn't change and no 301 is sent. A redirect changes the address and tells search engines the page has moved.
Should I use 301 or 302?
Use 301 for a permanent move or when attaching a secondary domain to the main one. A 302 signals a temporary jump, and search engines may keep treating the old address as the main one.
How long do DNS changes take to apply?
It depends on the record's TTL and on provider caches, so there is no guaranteed time. To make the switch faster, lower the TTL before you change the records.
Let’s look at your task for free
Leave your contact — in a 15-minute call we’ll show where leads get lost and what to fix first.