Coder Legion - Recent posts tagged zoho

How to Set Up a Free Custom Domain Email with Zoho Mail, Cloudflare, and Your Own Domain

Wed, 19 Aug 2026 15:16:34 +0000

How to Set Up a Free Custom Domain Email with Zoho Mail, Cloudflare, and Your Own Domain

A custom email address like contact@yourdomain.com makes a huge difference when you are building a personal brand, portfolio, or freelance presence. It looks more professional than a free Gmail address, and it is surprisingly easy to set up using Zoho Mail’s free plan and your domain’s DNS.

In this guide, I will walk through the exact flow I used to create a professional email address on a custom domain, without paying for a traditional business email suite.

Important: This post uses placeholder values instead of real DNS records, IPs, or credentials. Replace the examples with the values Zoho shows for your own account.

What you will need

Before you begin, make sure you already have:

A domain name (for example, yourdomain.com)
DNS access in Cloudflare or your domain provider
A Zoho Mail account
A few minutes to add DNS records and wait for propagation

For this setup, I used:

Website hosting: Vercel
DNS: Cloudflare
Email provider: Zoho Mail

That combination works very well for a personal website or portfolio.

Why use Zoho Mail?

Zoho Mail is useful because it lets you create a professional email address using your own domain. On the free plan, Zoho supports a single domain with up to 5 users, 5 GB of storage per user, and web-only access. The free plan is available only in select data centers, so availability may vary by region.

For a personal website, that is usually more than enough.

The overall flow

Here is the setup in simple terms:

Buy a domain.
Sign up for Zoho Mail.
Add your existing domain.
Verify that you own the domain using a TXT record.
Add MX records so mail is delivered to Zoho.
Add SPF, DKIM, and DMARC for email authentication.
Test sending and receiving mail.

Go to Zoho Mail’s signup page and choose the free plan.

During signup, Zoho will ask whether you want to add a new domain or an existing one. Since you already own the domain, choose Add an existing domain.

Enter your domain exactly as it should appear, for example:

yourdomain.com

Do not type www.yourdomain.com for email setup. Email should be configured on the root domain.

Step 2: Verify domain ownership

Zoho will ask you to prove that you own the domain. The simplest method is to add a TXT record in Cloudflare DNS.

Zoho will give you a TXT value similar to this:

zoho-verification=zbXXXXXXXX.zmverify.zoho.in

In Cloudflare, add a new DNS record:

Type	Name	Content
TXT	@	`zoho-verification=zbXXXXXXXX.zmverify.zoho.in`

If Cloudflare does not accept @, use the root domain name directly.

After saving the record, go back to Zoho and click Verify TXT Record.

Once that works, Zoho knows the domain belongs to you.

Step 3: Create your mailbox

After verification, Zoho will let you create the first user account for your domain.

For a personal site, a good choice is:

contact@yourdomain.com

You can also create:

hello@yourdomain.com
shubham@yourdomain.com
resume@yourdomain.com
jobs@yourdomain.com

If you only want one inbox, use aliases later instead of creating multiple mailboxes.

Step 4: Add MX records in Cloudflare

MX records tell the internet where your email should be delivered.

Without MX records, people can send mail to your domain name, but no one will know which server should receive it.

Add the MX records Zoho provides for your data center. For Zoho’s India region, the records usually look like this:

Type	Name	Mail Server	Priority
MX	@	mx.zoho.in	10
MX	@	mx2.zoho.in	20
MX	@	mx3.zoho.in	50

In Cloudflare DNS:

Type: MX
Name: @
Content: mx.zoho.in / mx2.zoho.in / mx3.zoho.in
Priority: 10, 20, 50

Do not proxy MX records. Cloudflare handles them as DNS-only records.

Step 5: Add SPF

SPF tells the world which servers are allowed to send email for your domain.

Add this TXT record:

v=spf1 include:zoho.in ~all

In Cloudflare:

Type	Name	Content
TXT	@	`v=spf1 include:zoho.in ~all`

What SPF means

This says:

Zoho is allowed to send mail for your domain.
Other servers should not be trusted by default.

This helps reduce spoofing and improves inbox delivery.

Step 6: Add DKIM

DKIM adds a digital signature to outgoing email. It helps receivers confirm that the message really came from your domain and was not modified in transit.

Zoho will generate a DKIM public key for you. The record usually looks like this:

Type	Name	Content
TXT	zmail._domainkey	`v=DKIM1; k=rsa; p=YOUR_LONG_PUBLIC_KEY_HERE`

What to do

Open Zoho Admin Console.
Go to DKIM settings.
Generate the DKIM record.
Copy the full TXT value into Cloudflare.
Save the record.
Return to Zoho and verify it.

DKIM verification can take a little longer than SPF because DNS propagation and verification caches may not update instantly.

Step 7: Add DMARC

DMARC is the policy layer that sits on top of SPF and DKIM.

It tells receiving mail servers what to do when authentication fails.

A good starting DMARC record for a personal domain is:

v=DMARC1; p=quarantine; pct=100; adkim=r; aspf=r; rua=mailto:contact@yourdomain.com; ruf=mailto:contact@yourdomain.com

In Cloudflare:

Type	Name	Content
TXT	_dmarc	`v=DMARC1; p=quarantine; pct=100; adkim=r; aspf=r; rua=mailto:contact@yourdomain.com; ruf=mailto:contact@yourdomain.com`

What these parts mean

p=quarantine → suspicious messages should go to spam
pct=100 → apply this policy to all mail
adkim=r → relaxed DKIM alignment
aspf=r → relaxed SPF alignment
rua → aggregate reports
ruf → forensic reports

For most personal domains, relaxed alignment is the simplest and safest choice.

Step 8: Wait for propagation

After you add the records, the changes need time to spread across DNS resolvers.

Usually:

TXT records propagate quickly
MX records may take a little longer
Zoho’s dashboard may still show red or pending status even when everything is already working

Do not panic if Zoho’s UI is slow to update.

A good way to confirm is to test real mail flow.

Step 9: Test sending and receiving

Send a test email from your Zoho mailbox to Gmail.

Then reply from Gmail back to your custom domain email.

If both directions work, the setup is operational.

You can also check the message headers in Gmail to confirm:

SPF: pass
DKIM: pass
DMARC: pass

That is the best real-world proof that your setup is correct.

Common issues and fixes

1. Zoho still shows MX in red

If mail is already working, the DNS is usually fine. Wait for propagation and check again later.

2. SPF is green but DKIM is still pending

That usually means the DKIM TXT record is correct but Zoho has not rechecked it yet, or the record was added recently.

3. Email is landing in spam

Check all three:

SPF
DKIM
DMARC

Also make sure your domain is not sending from an unauthorized service.

4. Cloudflare says the record already exists

Double-check for duplicates. You should have only one SPF TXT record and one DKIM TXT record for each selector.

Optional improvements

Once the core setup works, you can make it even better:

Create aliases

A single inbox can receive mail for multiple addresses such as:

contact@yourdomain.com
hello@yourdomain.com
resume@yourdomain.com
jobs@yourdomain.com

Add a signature

A clean signature makes every email look more professional:

Shubham Singh
DevOps / DevSecOps Engineer

Website: https://yourdomain.com
LinkedIn: linkedin.com/in/your-link
GitHub: github.com/your-handle
Email: contact@yourdomain.com

Use your custom email everywhere

Replace your Gmail address on:

Portfolio website
Resume
LinkedIn contact info
Job applications
GitHub profile
Freelance profiles

That keeps your brand consistent.

What this setup gives you

This setup is not end-to-end encrypted email, but it does give you:

Professional custom email
TLS encryption in transit
SPF authentication
DKIM signatures
DMARC protection
Better inbox deliverability
A clean personal brand

For a portfolio or professional website, this is exactly what you want.

Final DNS record checklist

Here is the full checklist in one place:

Record	Purpose	Example
TXT	Zoho domain verification	`zoho-verification=zbXXXXXXXX.zmverify.zoho.in`
MX	Incoming mail delivery	`mx.zoho.in`, `mx2.zoho.in`, `mx3.zoho.in`
TXT	SPF	`v=spf1 include:zoho.in ~all`
TXT	DKIM	`v=DKIM1; k=rsa; p=...`
TXT	DMARC	`v=DMARC1; p=quarantine; ...`

Conclusion

With a domain, Cloudflare DNS, and Zoho Mail’s free plan, you can build a fully professional email address without paying for a large business email suite.

For a personal portfolio, that is one of the best low-cost upgrades you can make.

It improves your credibility, looks cleaner on your website, and gives your project a more polished finish.

Cloud IMS vs. On-Premise: What Small Manufacturers Get Wrong When Energy Bills Spike

Sat, 18 Apr 2026 10:31:42 +0000

Small manufacturing units in the U.S. and EU have spent the last several years absorbing one financial shock after another, supply chain disruptions, labor shortages, and raw material volatility. But the energy price surge that ran through 2022 and has remained structurally elevated since has introduced a quieter, slower-burning problem. Even after the closure of the Strait of Hormuz, energy costs spiked worldwide. It lives inside server rooms. It runs through cooling units. It hums inside UPS systems at 3 a.m. when the floor is empty, and the meters are still spinning.

The choice between a cloud-based inventory management system and a customized on-premises solution used to be a debate between control and convenience. Today, for a small manufacturer watching their utility bill compete with their payroll, the question has real financial consequences. Get it wrong, and you're not just paying for software — you're funding infrastructure that works against your margins every single hour it runs.

This is not a buyer's guide. It is an honest technical and financial analysis of what both approaches actually cost, what they demand from your infrastructure, and which one holds up better when industrial electricity rates stop cooperating.

Defining the Playing Field

A cloud-based inventory management system — cloud IMS — is software hosted on remote servers, accessed through a browser or app. You pay a monthly or annual subscription. The vendor handles uptime, updates, security patches, and backups. Platforms like Fishbowl Online, inFlow Cloud, Cin7, Zoho Inventory, and the inventory modules inside NetSuite or SAP Business One Cloud all fall into this category.

A customized on-premise solution is software deployed on servers you own, inside your facility or a private data center. It can be built on open-source platforms like Odoo or ERPNext, heavily modified to fit your workflow, or it can be a proprietary system developed by a contracted software firm. You own the code, the data, and the hardware — along with every maintenance obligation, security responsibility, and hardware failure that comes with that ownership.

The word "customized" carries real weight here. A stock on-premise install is one thing. A solution tailored to your specific shop floor systems, barcode infrastructure, EDI requirements, and reporting workflows is a fundamentally different undertaking in terms of both capability and ongoing cost.

The Tech Stack, Cracked Open

Inside a cloud IMS

Most cloud inventory management platforms run on a multi-tenant SaaS architecture. At the application layer, you're typically looking at React or Vue.js handling the frontend, with Python, Node.js, or Ruby on Rails running the backend logic. Databases are usually PostgreSQL or MySQL for relational inventory and order data, with Redis layered on top for caching and Elasticsearch powering fast SKU-level search across large catalogs.

The infrastructure beneath this is what changes the energy conversation entirely. These vendors operate on hyperscale cloud infrastructure — AWS, Google Cloud, or Azure data centers running at Power Usage Effectiveness ratios of 1.1 to 1.2. They waste very little electricity relative to actual compute output. Your cloud IMS vendor is not wasting power. It is running at economies of scale you cannot come close to replicating in a factory-floor server closet in Ohio or Stuttgart.

REST APIs and native integrations are standard. Modern cloud IMS platforms connect directly to QuickBooks, Shopify, Amazon Seller Central, major 3PL providers, and shipping carriers without custom development work. You configure, not build. That distinction matters significantly when your IT presence is a part-time contractor or a generalist office manager wearing too many hats.

Connectivity is the hard dependency. The entire model assumes reliable internet. Most platforms now offer offline-capable mobile apps with sync-on-reconnect, but core reporting, purchasing workflows, and multi-location visibility require a live connection.

Inside a customized on-premise solution

The stack varies by implementation, but the most common serious deployment for a small U.S. or EU manufacturer is ERPNext or Odoo deployed on owned hardware with custom modules built on top.
ERPNext runs on Python and JavaScript, with MariaDB as the primary database, NGINX as a reverse proxy, Gunicorn serving the application layer, and Redis managing caching and background job queuing. The whole system runs on Linux — typically Ubuntu Server LTS. Hardware requirements are modest for a small operation: a dedicated server with 16–32GB RAM and a mid-range Xeon or EPYC processor handles most small manufacturing workloads without strain.

Where on-premise genuinely earns its differentiation is shop floor integration. Using OPC UA or Modbus TCP protocols, a custom on-premises system can communicate directly with PLCs and SCADA systems on your production floor. Stock levels can update automatically from machine cycle counts rather than manual entries. Bill of Materials consumption can be triggered by actual production output. Scrap reporting can flow from equipment directly into stock valuation without a human touching a keyboard. Cloud IMS platforms are improving in this area, but they're designed for the median customer — a business without PLCs. If your floor has real industrial complexity, out-of-the-box cloud integrations will feel like wearing someone else's work boots.

Infrastructure Reality vs. the Sales Pitch

On paper, the on-premise case is compelling. You own your data, control your customization, and face no recurring subscription fees. In reality, the infrastructure situation inside most small manufacturing facilities is considerably messier.

Server rooms in small factories are frequently afterthoughts — a rack in a storage corridor, cooled by a window unit sharing a circuit with production equipment, protected by a UPS last load-tested during a prior administration. The thermal management burden alone is material. A server drawing 300–500 watts continuously requires active cooling to stay within operating range. In a facility where ambient temperatures climb during summer production runs, that cooling load compounds. You're not just powering the server — you're powering the system, keeping the server alive.

Cloud IMS shifts that burden entirely to the vendor. Your endpoints — laptops, tablets, warehouse barcode scanners — draw 20–45 watts under load. The energy footprint of your IT infrastructure drops dramatically. The tradeoff is that you're now dependent on internet reliability, which has its own infrastructure cost: for serious cloud operations, most manufacturers need a primary broadband connection and a cellular or secondary line as a failover. That's an ongoing monthly expense that doesn't appear in the IMS subscription price.

Running the Energy Numbers for U.S. and EU Manufacturers

Let's put real shape around the cost difference for a small manufacturing operation — say, 20 to 50 employees, single facility.

A functional on-premise server environment — primary server, backup or redundancy unit, UPS, and dedicated cooling — draws between 800 watts and 1.5 kilowatts continuously, depending on hardware generation and ambient conditions. U.S. industrial electricity rates currently average $0.08 to $0.13 per kWh, with notable regional variance. At a 24-hour operation, that server infrastructure costs between $560 and $1,700 per year in electricity alone. In the EU, where industrial rates have ranged from €0.15 to €0.30 per kWh across Germany, France, Italy, and the Netherlands since the 2022 energy crisis, the same infrastructure runs between €1,050 and €3,940 annually — just in power. That figure excludes hardware refresh cycles, maintenance contracts, and any IT labor.

Cloud IMS subscriptions for a 20–50-person manufacturing operation typically cost $150 to $500 per month, depending on the platform, number of users, and feature tier. That puts the annual software cost between $1,800 and $6,000. Add $150 to $300 per month for redundant internet connectivity, and you're looking at a total annual operational cost of $3,600 to $9,600.

On raw numbers, neither is cheap. But the structural difference matters: on-premise infrastructure costs are directly correlated with energy prices. When your utility rate spikes, your server costs spike automatically. Your cloud subscription is a fixed contract. That pricing predictability has genuine operational value when you're trying to hold a budget in a volatile utility environment — and when you're in Germany or California, where rate volatility has been severe, that stability isn't a small thing.

The Customization Argument, Fairly Assessed

On-premise wins the customization debate, and it isn't particularly close — but the win comes with strings.

A well-built on-premise system can be wired into the actual manufacturing process at a level that cloud platforms cannot match without significant additional engineering. Real-time stock depletion from machine output. Automatic quality holds the lock inventory records. Supplier-specific EDI formatted to exact trading partner specifications. Custom costing models that reflect your actual overhead allocation. These aren't features you toggle on from a settings menu — they're coded integrations that require skilled developers who understand both your industrial environment and the software layer.

The ongoing maintenance costs of deep customization are what on-premises advocates consistently understate. Every platform update requires regression testing against your custom code. Every new shop floor system integration has to be built from scratch. Developer rates for Odoo or ERPNext specialists in the U.S. run $95 to $175 per hour. A meaningful customization engagement — say, integrating three shop floor systems, customizing costing logic, and building an EDI pipeline — can run $40,000 to $120,000 in professional services, with annual maintenance thereafter.

Cloud IMS platforms have narrowed this gap meaningfully in recent years. Platforms like Cin7 and NetSuite now offer webhook frameworks and open APIs that enable reasonably deep integration without requiring server ownership. But they're still building for the median manufacturer, not for your specific process, and the ceiling of what's configurable without touching source code is real.

Security, Data Control, and Compliance

This dimension gets less attention than it deserves in small manufacturing conversations.
On-premises keeps your data inside your building. For manufacturers operating in defense supply chains, pharmaceutical production, specialty chemicals, or any environment with ITAR, CMMC, or FDA 21 CFR Part 11 requirements, this is frequently non-negotiable. No vendor SLA substitutes for physical custody of your own data.

Reputable cloud IMS vendors maintain SOC 2 Type II certification, encrypt data in transit and at rest, provide role-based access controls, and offer detailed audit logging. The security investments these vendors make are likely more rigorous than those most small manufacturers can implement independently. But your data lives in a shared infrastructure environment, and your vendor's internal security practices remain opaque to you. For most small manufacturers in standard commercial sectors, this is a manageable and theoretical risk. For those in regulated supply chains, it may disqualify cloud options outright without significant additional configuration and compliance documentation.

EU manufacturers face the additional layer of GDPR compliance, which requires careful attention to where data is stored and processed. Most major cloud IMS vendors now offer EU data residency options — AWS Frankfurt, Azure Netherlands North — but confirming that your specific configuration actually keeps data within EU jurisdiction requires due diligence that many small operations skip.

Which One Actually Fits a Small Manufacturing Unit Right Now

There is no universal answer, but there is an honest framework.

If your operation has fewer than 50 employees, limited internal IT capability, standard commercial supply chain requirements, and you're in a region where industrial electricity rates have been volatile or rising, cloud IMS is almost certainly the more financially rational choice today. The subscription cost is visible, predictable, and disconnected from energy market swings. Your IT infrastructure energy footprint drops to near zero. You get enterprise-grade security and uptime without enterprise-grade overhead. The integrations you need for procurement, accounting, and order management are likely already in place.

If your operation has complex shop floor systems, regulated supply chain requirements, deep process-specific customization needs, or existing on-premise infrastructure that is already paid off and well-maintained, a customized on-premise solution remains defensible. The energy cost is real but not ruinous if your hardware is modern and your cooling is efficient. The customization ceiling is genuinely higher. And if internet reliability at your industrial location is poor, making your inventory system dependent on a broadband connection is a genuine operational risk.

The mistake most small manufacturers make is treating this decision as permanent. Cloud IMS contracts are typically annual. On-premise infrastructure can be decommissioned or migrated. The real question is not which option is theoretically better — it's which option fits your actual cost structure, your actual technical environment, and your actual risk tolerance right now, with energy prices where they are and IT budgets where they are.

The answer to that question is almost always written somewhere in your last twelve utility bills. Start there.

Coder Legion - Recent posts tagged zoho

How to Set Up a Free Custom Domain Email with Zoho Mail, Cloudflare, and Your Own Domain

How to Set Up a Free Custom Domain Email with Zoho Mail, Cloudflare, and Your Own Domain

What you will need

Why use Zoho Mail?

The overall flow

Step 1: Sign up for Zoho Mail

Step 2: Verify domain ownership

Step 3: Create your mailbox

Step 4: Add MX records in Cloudflare

Step 5: Add SPF

What SPF means

Step 6: Add DKIM

What to do

Step 7: Add DMARC

What these parts mean

Step 8: Wait for propagation

Step 9: Test sending and receiving

Common issues and fixes

1. Zoho still shows MX in red

2. SPF is green but DKIM is still pending

3. Email is landing in spam

4. Cloudflare says the record already exists

Optional improvements

Create aliases

Add a signature

Use your custom email everywhere

What this setup gives you

Final DNS record checklist

Conclusion

Cloud IMS vs. On-Premise: What Small Manufacturers Get Wrong When Energy Bills Spike

Defining the Playing Field

The Tech Stack, Cracked Open

Inside a cloud IMS

Inside a customized on-premise solution

Infrastructure Reality vs. the Sales Pitch

Running the Energy Numbers for U.S. and EU Manufacturers

The Customization Argument, Fairly Assessed

Security, Data Control, and Compliance

Which One Actually Fits a Small Manufacturing Unit Right Now