Setting Up Zoho Mail With Your Own Domain: A Complete Nepal Walkthrough

Most Zoho Mail setups that go wrong don't go wrong inside Zoho. They go wrong at the domain registrar's DNS panel, where a mistyped record or a missing verification code leaves mail bouncing for days. We've set up Zoho Mail for hundreds of Nepali businesses running domains through DotNepal, GoDaddy, Namecheap, and WebsNP's own registration service, and the process is the same everywhere once you know the order to do things in.

What You Need Before You Start

You need admin access to your domain's DNS panel (not just the website hosting panel — these are often different logins), and a Zoho Mail account, either the free tier or a paid plan depending on how many mailboxes you need. If you don't have DNS access yourself and your website was set up by a developer or a previous agency, get that access first; nothing below works without it.

Step 1: Add and Verify Your Domain in Zoho

Inside Zoho Mail's admin console, add your domain and choose a verification method. The simplest for most Nepali businesses is a TXT record: Zoho gives you a specific value, you add it as a TXT record in your DNS panel, and Zoho checks for it. This alone doesn't activate email, it just proves you own the domain, but skipping it stops everything else.

Step 2: Add the MX Records (This Is Where Most Setups Break)

MX records tell the internet where to deliver mail for your domain. Zoho requires you to add specific MX records pointing to Zoho's mail servers, in a specific priority order. The most common mistake here is leaving an old host's MX record in place alongside the new Zoho ones — mail servers will pick whichever priority is lowest, so a leftover record from your old host can silently steal incoming mail for weeks before anyone notices a client's email never arrived.

Step 3: Add SPF, DKIM, and (Ideally) DMARC Records

• SPF tells receiving mail servers that Zoho is authorized to send mail for your domain. Without it, your outgoing mail is far more likely to land in spam.
• DKIM digitally signs your outgoing mail so receivers can verify it wasn't forged in transit. Zoho generates the DKIM key; you add it as a TXT record.
• DMARC tells receiving servers what to do if SPF or DKIM checks fail. It's optional in Zoho's setup flow but worth adding — it's one of the biggest single factors in whether your invoices and quotes land in a client's inbox instead of their spam folder.

Step 4: Create Mailboxes and Set Up Clients

Once DNS is verified, create individual mailboxes for your team inside the Zoho admin console. Each user can then access mail through Zoho's webmail, the Zoho Mail mobile app, or a desktop client like Outlook or Apple Mail using IMAP settings Zoho provides. For a small Nepali business, we typically recommend starting everyone on Zoho's webmail and mobile app first, since it needs zero configuration beyond a login, and adding desktop clients only for staff who specifically want them.

Common Mistakes That Cause Delays

The same handful of errors account for most delayed setups we see: adding MX records but forgetting to remove old ones from a previous host, adding a TXT record with extra quotation marks the DNS panel didn't strip automatically, and not waiting for DNS propagation (which can take anywhere from a few minutes to 24-48 hours depending on your registrar) before assuming something is broken. Check propagation with a tool like whatsmydns.net before troubleshooting further.

Getting Help If DNS Feels Unfamiliar

DNS panels look different at every registrar, and getting an MX priority number wrong is an easy, invisible mistake to make. WebsNP sets up Zoho Mail on your domain as part of our service, in NPR with eSewa and Khalti accepted, and our Nepali team on WhatsApp will make the actual DNS changes with you rather than sending a generic help article and leaving you to it. If you're mid-setup and stuck, send us your domain and registrar and we'll tell you exactly what's missing.