1C-Bitrix Domain Binding: Setup and Optimization Guide

How to Bind Domains to Sites in 1C-Bitrix: Full Setup Guide

Consider this scenario: two domains on one server, but both open the same site. This is a common issue faced by many. As a team of Bitrix developers with 8 years of experience, we frequently encounter this task. Just last year we configured domain binding bitrix for 50+ projects — from simple online stores to complex multilingual portals. Let's break down why this happens and how to configure it correctly so each domain leads to its own site, while saving on maintenance costs.

How Bitrix Determines the Current Site and Why Problems Occur

On each request, the Bitrix kernel reads the b_lang table and looks for a record where the SERVER_NAME field matches the HTTP Host header of the incoming request. The found LID (two-letter site code) is then used for all operations: template selection, information blocks, language, etc. This is the core of domain setup bitrix.

SELECT LID, DIR, NAME, SERVER_NAME FROM b_lang WHERE ACTIVE = 'Y';

If SERVER_NAME does not match any record — Bitrix uses the first default site or returns an error depending on the configuration. This is the reason "all domains show one site." We see this issue in every third project where domain configuration was not performed.

How to Add a Domain to a Site via the Admin Panel

In /bitrix/admin/site_edit.php?LID=<site_code>, fill in the "Server domain name" (SERVER_NAME) field. Enter the domain without http:// and trailing slash: example.com.

If the site should work on both www.example.com and example.com — choose one as the primary, and set up the second as a redirect at the web server level (nginx/Apache), not via Bitrix. Do not try to specify both in SERVER_NAME — the field does not support multiple values.

The DIR field is the directory path relative to the root. For the main site — /. For a second site on the same server — /second/ or the same / if sites are differentiated only by domain. In 80% of cases, the problem is solved by correctly filling in DIR.

Web Server Configuration: What You Need to Know

Bitrix handles routing within its kernel, but the web server must accept requests to the required domains and pass them to the Bitrix root.

Nginx: For each domain, a separate server{} block or a common block with server_name example.com example2.com. The document root is the same — the Bitrix installation root. This is the standard nginx bitrix domain configuration.

server {
    listen 80;
    server_name example.com www.example.com;
    root /var/www/bitrix;
    # ... standard Bitrix configuration
}

HTTPS: Each domain needs its own SSL certificate or a wildcard/multi-domain certificate. Let's Encrypt issues certificates for multiple domains via certbot --domains example.com,example2.com. Without HTTPS, search engines penalize sites, potentially dropping rankings by 20%.

How to Set Up Multisite in 5 Steps

1. Create a new site in the admin panel (LID code, name, language).
2. Specify the domain in the SERVER_NAME field.
3. Define DIR: if sites differ only by domain, set / for both.
4. Configure the web server: separate server block for each domain with a common root.
5. Issue SSL certificates for each domain and test redirects.

This process takes from 1 to 3 days for an experienced engineer. We have refined it to automation — thanks to ready-made configuration templates. Our cost for basic multisite bitrix setup starts at $500.

Why Multisite on Bitrix is More Beneficial Than Separate CMS Instances

Compare: one core, a unified update pool, shared users and modules — versus several isolated installations. Here's a table:

We see in practice that multisite reduces update and maintenance time by 2–3 times. Multisite is 2-3 times better than separate installations in terms of maintenance efficiency. Licensing costs drop by 40% compared to purchasing the "Business" edition for each site separately. For example, licensing costs for three separate Business edition licenses can exceed $1,000 per year, whereas a single multisite license costs around $600, saving you $400 per year.

Domain Masking: When Is It Needed?

Scenario: a main domain main-shop.ru and a partner domain partner-shop.ru that should show the same site but with different branding. In Bitrix, this is implemented by checking $_SERVER['HTTP_HOST'] in init.php or in the site template with conditional loading of a different template — this is not standard multisite, but a custom solution. This is the core of domain masking bitrix.

Standard multisite involves different templates, languages, and content for each site. If you need the same content on different domains — use a canonical url bitrix attribute in <head> to specify the main domain and avoid SEO duplication.

How to Perform a Site Migration?

When changing the domain, update SERVER_NAME in b_lang, then check:

• $_SERVER['HTTP_HOST'] settings in /bitrix/.settings.php (if explicitly set)
• Site URL in module settings: COption::GetOptionString("main", "server_name") — in some versions it is stored there
• Links in infoblock content — absolute links like http://old-domain.ru/... must be replaced via SQL queries to b_iblock_element_prop_s* and b_iblock_element
• Email templates in the main module — often contain hardcoded URLs

After migration, be sure to set up a 301 redirect from the old domain to the new one. Traffic losses can reach 30% without redirects. This is the key aspect of site migration bitrix.

What Our Domain Binding Setup Includes (Deliverables)

We perform turnkey setup, with the following deliverables:

• Audit of current domains and b_lang table
• Web server configuration (nginx/Apache) with SSL certificates
• Multisite or masking configuration
• Canonical URL checks and duplicate elimination
• Testing all domains (redirects, HTTPS, speed)
• Documentation and access handover
• Training for your team and ongoing support for 30 days

We evaluate the project after analysis — contact us for a consultation. Typically, basic configuration of one site takes from one day to three, depending on complexity (SSL, redirects, content migration). Order setup from us — we guarantee a documented scheme and a ready solution.

Learn more about multisite in the official documentation.

What Professional 1C-Bitrix Installation Includes

We start by checking innodb_buffer_pool_size. The default MySQL value (128 MB) is a death sentence for an online store with a catalog of 10,000+ items. We set 70–80% of available RAM on a dedicated server, 50% on VPS. This single setting speeds up the site by 2–3 times compared to the default. We'll assess your project in one day — get a consultation. Contact us to order turnkey installation with performance guarantee.

How to Choose Hosting and Edition for 1C-Bitrix Installation?

BitrixVM is a virtual machine with a pre-installed stack: nginx + Apache, PHP-FPM, MySQL/MariaDB, Sphinx, Push server. For VPS — the best start. Everything is already configured for Bitrix, including OPcache, log rotation, and firewall. Management via web panel on port 8890. Bitrix documentation recommends starting with BitrixVM for predictable performance.

VPS/VDS is the sweet spot. Minimum configuration for a medium online store: 2 vCPU, 4 GB RAM, SSD. Optimal: 4 vCPU, 8 GB RAM. OS: Ubuntu 22.04 or Debian 12. If not BitrixVM, we configure the stack manually for the task. Virtual hosting — only for business cards and landing pages. Requirements: PHP 8.0+, MySQL 5.7+ / MariaDB 10.0+, 512 MB RAM, .htaccess. 1C-Bitrix hosting partners guarantee compatibility. Dedicated server — for highload. Typical architecture: web server separate, database separate, Redis/Memcached separate. For Enterprise edition — web cluster with load balancer. Cloud (Yandex Cloud, VK Cloud, Selectel) — when load spikes: sales, seasonal peaks. Autoscaling via Managed Kubernetes or simple VM vertical scaling.

Choosing the edition is equally important. A common mistake: choosing "Small Business" for a store that grows to B2B with wholesale prices and three warehouses in six months. Upgrading to "Business" — pay the difference, data is not lost, but it's better to plan ahead. Our specialists select the edition for current tasks and with room for growth. For example, the "Business" license (about 35,000 RUB) pays off through multi-warehouse and 1C exchange, while the wrong choice can lead to a loss of up to 30,000 RUB monthly on excess resources.

What Server Settings Are Critical for 1C-Bitrix?

Web Server and PHP

nginx as reverse proxy + Apache (mod_php) or nginx + PHP-FPM directly. The second option saves memory — Apache is not needed. But some Bitrix modules use .htaccess, so for compatibility we sometimes keep Apache. nginx configuration: fastcgi_read_timeout 300 — for long operations (1C import), client_max_body_size 1024m — large file uploads. Block access to .settings.php, .settings_extra.php, bitrix/.settings.php — they contain database passwords. Rewrite rules from urlrewrite.php — Bitrix generates them, but with nginx + PHP-FPM they need to be duplicated. PHP 8.0–8.2 with extensions: mbstring, curl, gd, xml, json, opcache, redis/memcached. Key php.ini settings: opcache.memory_consumption=256, opcache.max_accelerated_files=20000, max_execution_time=300, memory_limit=512M, upload_max_filesize=100M, post_max_size=128M.

Database and Caching

MySQL/MariaDB. Key my.cnf parameters: innodb_buffer_pool_size — 70–80% RAM, innodb_log_file_size=256M, tmp_table_size=256M, max_heap_table_size=256M, thread_pool_size — number of CPU cores. Encoding utf8mb4 mandatory, otherwise emoji and special characters break. Redis is preferable to Memcached for Bitrix — supports persistent connections and is more reliable. In production, Redis handles concurrent writes three times faster than Memcached under typical load. Configure in .settings_extra.php:

'cache' => ['value' => ['type' => ['class_name' => '\\Bitrix\\Main\\Data\\CacheEngineRedis']]]
'session' => ['value' => ['mode' => 'default', 'handlers' => ['general' => ['type' => 'redis']]]]

sudo apt install redis-server
sudo systemctl enable redis

SSL, Email, and Cron

SSL — Let's Encrypt via certbot in 90% of cases. Redirect HTTP → HTTPS (301), HSTS, TLS 1.2/1.3, OCSP Stapling. In Bitrix, switch to HTTPS in the main module settings. Email: abandon mail() — connect SMTP (Yandex.Mail for domain, Mail.ru for Business). Be sure to configure SPF, DKIM, DMARC. Without SPF, emails go to spam. Test deliverability via mail-tester.com — score 9+/10. Cron: Bitrix agents switch to system cron — * * * * * /usr/bin/php /var/www/bitrix/modules/main/tools/cron_events.php. Schedule 1C exchange (15–60 min), search reindex, backups (mysqldump + rsync, rotation 7+4), temporary file cleanup.

Security and Administration

File system: owner www-data, directories 755, files 644, upload 775. nginx blocks access to configuration files. Enable Bitrix Proactive Protection — WAF, activity control (block after 5 failed attempts), kernel integrity check. For admin panel: two-factor authentication via Google Authenticator or OTP, restrict access by IP via nginx for paranoid.

How Long Does 1C-Bitrix Installation and Configuration Take?

Post-Installation Checklist

1. Performance Monitor (/bitrix/admin/perfmon_panel.php) — aim for 30+ points. Below 20 means serious configuration issues.
2. System Check — automatic check of all parameters. Red items must be fixed, yellow — case by case.
3. Security Scanner — check for typical vulnerabilities.
4. PageSpeed Insights — TTFB < 200ms on VPS, LCP < 2.5s.
5. Test 1C exchange — if integration is planned, verify CommerceML exchange before launch.

Additionally, check software versions, caching settings, cron operation, SSL certificate, SPF/DKIM/DMARC, access rights, delete default users and pages. For projects with 54-FZ, ensure fiscalization is configured via OFD provider.

Deliverables

• Fully configured server for 1C-Bitrix with MySQL, PHP, nginx optimization.
• Installed and activated license of the required edition.
• SSL certificate, email settings, cron and backups.
• Documentation: all configuration parameters, access credentials, cron tasks.
• Content manager training: how to log into admin panel, add products, upload images.
• Post-installation support for 30 days — consultations on settings.

Why Trust Professionals with Installation?

Incorrect installation means lost time and money. We've seen projects where a store on "Start" couldn't handle 50 visitors because innodb_buffer_pool_size wasn't configured. After migrating to VPS with correct configuration, the site "flew". Incorrect configuration can cost 30,000 RUB monthly due to excessive resource consumption. You get a ready-made architecture that scales. Order turnkey 1C-Bitrix installation — get a reliable platform for business growth. Contact us for a free consultation: we'll calculate the cost and time for your project. Over 7 years of experience, 120+ Bitrix projects implemented, including highload stores with million-item catalogs. Get in touch — we'll help configure Bitrix for your project.