Skip to content
Innovialabs

How to Set Up Yandex 360 Mail on Your Own Domain

Practice4 min

In short

Add and verify your domain in the Yandex 360 admin panel, create MX (mx.yandex.net), SPF, DKIM and DMARC records wherever your DNS is managed, set up staff mailboxes, and mail starts arriving as soon as the records propagate.

The short answer

To receive mail at addresses like name@company.uz through Yandex 360, you go through five steps:

  1. Add the domain to your Yandex 360 organization and verify ownership.
  2. Create an MX record in DNS — it tells the world where to deliver your mail.
  3. Add SPF, DKIM and DMARC — without them, company mail tends to land in spam.
  4. Create staff mailboxes and aliases.
  5. Set up mail apps and phones.

Yandex 360 plans and limits change over time, so check the current terms for your team size before you start.

Step 1. Verify the domain

Add the domain in the Yandex 360 admin panel. The service offers a verification method — most often a TXT record like yandex-verification: ... in DNS, sometimes a meta tag or an HTML file on your site. The DNS option is more reliable because it does not depend on the website being up.

The key is knowing where your DNS is actually managed. If the domain was bought from one registrar but its NS servers point to, say, Cloudflare or your hosting provider, that is where the records must go.

Step 2. Add the DNS records

TypeNameValue
MX@mx.yandex.net., priority 10
TXT (SPF)@v=spf1 redirect=_spf.yandex.net
TXT (DKIM)mail._domainkeykey from the Yandex 360 panel (v=DKIM1; k=rsa; p=...)
TXT (DMARC)_dmarcv=DMARC1; p=none; rua=mailto:dmarc@company.uz

Notes:

  • MX must be the only one. Delete old MX records from your host or previous provider, or some mail will go there.
  • A domain can have only one SPF record. If your website or CRM also sends mail through another service, merge everything into one record: v=spf1 include:_spf.yandex.net include:<other service> ~all.
  • The DKIM key is generated in the domain settings of the admin panel. Copy it whole, without extra spaces or line breaks.
  • Start DMARC at p=none, which is monitoring mode. Once you are sure all legitimate mail passes, tighten the policy to quarantine or reject.

New records do not take effect instantly — it depends on TTL and DNS resolver caches.

Step 3. Create mailboxes and aliases

Add users in the staff section of the admin panel; each login becomes login@company.uz. Then:

  • Aliases are extra addresses for one person. For example, the head of sales uses a.karimov@ as the main address and sales@ as an alias.
  • Mailing lists (groups) are shared addresses delivered to several people: info@, support@.
  • Admin rights should go to at least two people so you never lose access to the organization.

It is best to create mailboxes and aliases before switching MX, so the very first messages find their recipients.

Step 4. Set up mail apps

The simplest option is the Yandex Mail web interface and mobile app — just sign in with the new address. For Outlook, Thunderbird or the built-in mail apps on iPhone and Android, use IMAP:

SettingValue
Incoming (IMAP)imap.yandex.ru, port 993, SSL
Outgoing (SMTP)smtp.yandex.ru, port 465, SSL
Usernamethe full address, e.g. name@company.uz

Two common blockers: you must allow IMAP access in the mail settings, and Yandex requires an app password for third-party apps instead of the regular account password.

Why mail is not arriving: common errors

  • Old MX records remain. Check with nslookup -type=mx company.uz — the answer should list only mx.yandex.net.
  • Records added in the wrong place. DNS was edited at the registrar while the domain is served by other NS servers.
  • Duplicated record name. The panel appends the domain itself, producing mail._domainkey.company.uz.company.uz.
  • Two SPF records. Separate records for Yandex and the website break the check — you need one combined record.
  • The mail host is proxied through Cloudflare. Mail-related records must be DNS-only.
  • Not enough time has passed. After changes, wait for the old records' TTL to expire.
  • The mailbox does not exist — mail to a missing address bounces back to the sender.

FAQ

Yes. The website is defined by A records and mail by the MX record. They are independent, so the site can stay wherever it is.

We can help with this

If you'd rather get the result than figure it all out yourself — this is what we do every day.

Discuss a project

Read next

Have an idea or a task? Tell us about it

We'll reply within one business day and propose a solution. The consultation is free.