Configure Custom Domain Email with Zoho and Now
In this guide I’m going to cover the configuring of your custom domain with Vercel’s Now platform using the Now CLI.
I’ll be primarily covering the steps you take after setting up an account with an email provider, the email provider I’m using is Zoho Mail if you don’t use either of these services then this guide may not be much use to you.
It’s implied that you have a machine set up for web development already and are familiar with using the terminal.
If you need to get set up for Windows I have written a guide previously on that topic.
If you’re a Linux user, check out this video on getting set up:
Zoho mail offer a 5 GB forever free plan, so as long as you can manage your email archiving then you are good to go.
You also get up to five users and a 25mb file attachment limit with hosting for a single domain.
Pretty good right!
When you sign up with Zoho Mail you will be prompted to create a super admin user for your zoho account and you’re given the opportunity to set up two factor authentication (2fa).
Zoho will even tell you about their authenticator app, which is only for authenticating with Zoho. Use this is you like, I use a 2fa app that you can use for multiple services.
You will be given a code to verify that you are the owner of the
domain, which you will need to add as a
TXT entry on your domain
with the Now CLI.
The verification token will look something like this:
Add that to your domain DNS with the Now CLI, you can check your
domain DNS entries with the
# list your dns entries now dns ls yourdomain.com # add the zoho verification as a TXT record now dns add yourdomain.com @ TXT zoho-verification=se4567894.zmverify.zoho.eu
Now to configure the
MX records. MX records are essential to receive
emails in your domain. The MX records for your domain will look
something like this:
|@ / Blank||mx.zoho.eu||10|
|@ / Blank||mx2.zoho.eu||20|
|@ / Blank||mx3.zoho.eu||50|
Add them much in the same way as with the verification token with the
Now CLI this time specifying an
MX instead of
TXT and there’s a
second argument for the priority:
now dns add yourdomain.com @ MX mx.zoho.eu 10 now dns add yourdomain.com @ MX mx.zoho.eu 20 now dns add yourdomain.com @ MX mx.zoho.eu 50
To ensure that valid emails from your domain get delivered to your users, and spoofed emails from other spammers are identified by the other email services, it’s recommend you add an SPF record for your domain.
This will go into a
TXT record like with the verification token:
now dns add yourdomain.com @ TXT 'v=spf1 include:zoho.eu ~all'
Note: You may need to wait a while after making these changes before the DNS updates can be verified via Zoho.
There's a reactions leaderboard you can check out too.