Many business owners register several domains at once to protect their brand: a .uz for local customers, a .com for foreign partners, and sometimes a common misspelling. That is a sensible move, but connecting them carelessly causes more harm than good. If every domain serves the site on its own, search engines see several copies of the same pages, and visitors notice the address bar switching between names. Here is how to bring all of them together under one address.
Choose the primary domain first
The first step is a decision, not a configuration change: under which address will the site permanently live? That is your primary domain, and every other name redirects to it. If most customers are in Uzbekistan, .uz is usually the natural choice; an export-focused company may prefer .com. Decide on www versus no www at the same time, because www.mebeluy.uz and mebeluy.uz are technically different hosts.
Imagine a furniture shop in Tashkent that owns mebeluy.uz and mebeluy.com. Its buyers are mostly local, so it picks mebeluy.uz without www. That leaves four names: mebeluy.uz, www.mebeluy.uz, mebeluy.com and www.mebeluy.com. Only the first serves content; the other three redirect permanently.
DNS: every name must reach the server
A redirect can only happen once the request reaches the server hosting the site. In each domain's DNS zone, create an A record pointing to the hosting IP and attach www to the bare name with a CNAME. If the second domain has no DNS at all, visitors get a "site not found" error and no redirect ever fires.
; mebeluy.com zone
mebeluy.com. 3600 IN A 203.0.113.10
www.mebeluy.com. 3600 IN CNAME mebeluy.com.
; mebeluy.uz zone
mebeluy.uz. 3600 IN A 203.0.113.10
www.mebeluy.uz. 3600 IN CNAME mebeluy.uz.Replace the sample address 203.0.113.10 with the real IP from your hosting cabinet, then confirm propagation with dig +short mebeluy.com A.
Adding the second domain on the hosting
Panels such as ISPmanager offer two options: add the extra domain as an alias of the existing site, or create a separate site that contains nothing but a redirect rule. Aliases are simpler, since all names share one folder and one configuration, and the redirect lives in a single .htaccess file. A separate site makes sense if you may later put something different on the second domain.
301 redirects to the primary address
Use a 301, which tells browsers and search engines that the move is permanent, so rankings and link value consolidate on the primary domain. A 302 is temporary and wrong for this job. On Apache hosting, these rules gather every name onto one HTTPS address while keeping the path and query string:
RewriteEngine On
# Leave the Let's Encrypt challenge path alone
RewriteCond %{REQUEST_URI} !^/\.well-known/acme-challenge/
# Wrong host or plain HTTP - send to the primary address
RewriteCond %{HTTP_HOST} !^mebeluy\.uz$ [NC,OR]
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://mebeluy.uz/$1 [R=301,L]With direct access to nginx, a dedicated server block does the same:
server {
listen 80;
listen 443 ssl;
server_name www.mebeluy.uz mebeluy.com www.mebeluy.com;
# ssl_certificate and ssl_certificate_key go here
return 301 https://mebeluy.uz$request_uri;
}The certificate must cover every name
A common mistake is issuing a certificate for the primary domain only. Someone typing https://mebeluy.com then sees a security warning before the redirect is even sent, because the server has to complete the TLS handshake with a valid certificate for that exact name first. Make sure your Let's Encrypt certificate lists all four names. On sayt.uz hosting the free Let's Encrypt certificate renews automatically; after adding aliases, just check that they were included.
Verify from the command line
Browsers cache old redirects, so test with curl instead:
curl -sI http://www.mebeluy.com/katalog?page=2 | grep -iE "^(HTTP|location)"
# Expected:
# HTTP/1.1 301 Moved Permanently
# Location: https://mebeluy.uz/katalog?page=2Ideally each name lands on the primary address in a single hop. Chains of three redirects slow the page down and waste crawler budget.
Site settings, search engines and email
Inside the site, canonical tags, the sitemap and internal links should all use the primary domain. In WordPress, a site address that does not match it can cause an endless redirect loop. Verify the primary domain in Google Search Console and Yandex Webmaster and submit the sitemap there. Finally, remember that web redirects do nothing for email: if the .com should receive mail, it needs its own MX records; if it never sends mail, publish v=spf1 -all so nobody can spoof it. Get these four pieces right once, primary name, DNS, 301 and SSL, and your brand stays protected while all search strength gathers on one address.