Getting Started


Can we use a registered domain hosted with another service provider?

Sure you can. During deployment your domain will be created on the SkyConnect servers.

How much time will it take in shifting from our existing mail server to the SkyConnect servers?

The provisioning of the domain takes one working day.

The next step of provisioning users can be done immediately if the user list is available in the right format.

The time for data migration depends on a variety of factors such as volume of data, data format, connectivity between the source setup and SkyConnect servers.  It is recommended that for large volumes, the data migration is done post go live.

The time taken for user on-boarding depends on the number of users, the geographical distribution, the availability of the IT teams at all locations and whether the users access using desktop or web clients.

The switch-over to the new system or the GoLive phase involves updating the DNS records for the domain. While the changes are small it may take some time for the new entries to reflect.

Go Live

How to test MX entries of a from a Linux desktop?

Use commands mentioned below to test MX entries in Linux
Host -t mx
host -t txt

How to Test current MX record in windows machine?

Follow the steps mentioned below to test current MX records in windows machineC:\> nslookup 
Default Server: 

> server 
Default Server: 

> set q=mx
Address: MX preference = 10, mail exchanger =

What are the tools on a Windows desktop to check MX records for a domain?

You can use nslookup from the command line.

What are the online tools available to check MX records for a domain?

You can test the MX Records from popular tools available on internet like

Does the migration require any downtime?

The Go live which is the final steps, requires a change in the DNS entries. While the changes are done by changing a few settings, it may take time for the new values to reflect across all the DNS servers around the world.

During this transition period, some mail will be delivered to the old email servers even after the changes to the DNS are done. So to avoid mail being split, it is advised to change the DNS settings in non peak hours. Usually around 8 pm for a company working 9-5.

How much time it will take to reflect the new DNS records?

When changing a record, it will take the length of the TTL (time to live) in seconds to expire before your new changes go into effect. You can set the TTL to any value before or after making changes to your records. Reasonable values for a static IP are anywhere from 12 hours (43200 seconds) to 24 hours (86400 seconds). Reasonable values for a Dynamic IP are between 5 and 120 seconds.

Domains which use Secondary DNS are scheduled to be added to the secondary DNS services no earlier than 2 hours after you enter the data into the system. This provides enough time to configure your primary DNS servers to allow AXFR/IXFR transfers to our secondary name servers. You should allow at least 48 hours for configuration changes to propagate before removing any previous name servers.

To confirm the changes,

  1. Go to
  2. Specify the domain name
  3. Verify the MX and TXT record.

What precautions should I take when making the DNS changes?

  • Be very careful while doing the DNS changes. Incorrect addition/modification/deletion of dns records may cause critical mail bounce issues.
  • Keep the Mithi Team well informed while performing the go live i.e. while making changes in DNS.
  • Test all the critical mail flow tests after doing the DNS changes.