Connect your domain to Business Email: MX, SPF, DKIM, DMARC and automatic setup records

1. Why do I need DNS records?

Email runs on your domain's DNS records. Without them, the internet does not know where to deliver mail for @examplecompany.com, and the mail you send looks "unauthenticated" to receiving servers and may land in spam.

The client area prepares the expected value of every record for you; you only copy and paste it into your DNS provider. You do not need to change your name servers (NS); your website and other records stay as they are.

All recommended records point to mx1.gyrohosting.com. In the client area they are grouped under Automatic setup (email + password only). Mail still works without them; you just have to type the server name by hand when you set up a device.

The imap., smtp. and mail. names and the security certificate

When these three names (and autoconfig, autodiscover) point to mx1.gyrohosting.com, our mail server adds them to its security certificate automatically. This happens at the next daily certificate renewal at the latest: within 24 hours of adding the record, usually overnight. Once that is done, imap.examplecompany.com (993) and smtp.examplecompany.com (465 or 587) work without warnings. Until then, if an app shows a certificate warning, use mx1.gyrohosting.com as the server name; it always works.

2. Before you start: the switch-over order

If your domain has working email somewhere else right now, change the MX record last. As soon as MX changes, new mail starts arriving with us, so your mailboxes must be ready and your old mail moved before that.

Recommended order:

1. Add the ownership verification TXT record and click Verify (this does not affect your current email).
2. Add the SPF, DKIM and DMARC records. Merge SPF with your existing record (Section 4).
3. Create your mailboxes in the client area.
4. Move your old mail with IMAP Migration in the client area.
5. Finally change the MX record, delete the old MX records and add the automatic setup records.

If this is a new domain that has never had email, you can add all records at once; verification completes automatically when MX points to us.

3. Step by step DNS setup

1. In the client area, open My Services and click your Business Email service.
2. Click the DNS Setup card on the service page (or under Setup › DNS Setup).
3. If the domain is not verified yet, a Verify domain ownership box appears at the top. Copy the Name (Host) (_gyromail) and Value lines.
4. At your DNS provider, create a TXT record with this information and save it.
5. Back in the client area, click Verify. You will see "Domain verified." If the record is not visible yet, try again in a few minutes.
6. For every row in the table, add a record with the same Type, Name (Host) and expected value at your DNS provider. The copy icon next to the value copies the full value (long values are shortened on screen).
7. Set the MX priority to 10.
8. Save at your DNS provider and click Check now in the client area.
9. Look at the status column: Correct, Wrong, Missing or Unreadable. When all required records are correct, the top of the page says "All required records are correct. Your email service is live."

The check runs live from our mail server and asks your domain's own name server first, so a record you just added usually shows up right away. You can use Check now at most once every 20 seconds. The system also checks your records every hour; if required records are still missing, you get reminder emails on day 1, 3 and 7 of the service.

If your domain's DNS is hosted by us: records are added for you

If we manage your domain's DNS, you do not need to add the records yourself:

The system also looks for missing records once a day. If your DNS is in Gyro DNS or in the Cloudflare account we manage, an Add records automatically button appears next to Check now and adds whatever is missing in one click.

Automatic adding follows two rules:

• It never overwrites an existing record with a different value. If another record already uses the name (for example mail points to your website or old mail server), that row is left as it is and the client area tells you which records were not changed.
• When records are added on their own, the automatic setup records are written only once MX points to us. While your mail is still elsewhere, phones are not sent to the wrong server.

If your DNS is with another provider (your registrar, your own Cloudflare account and so on), the client area says so and you add the rows from the table yourself.

4. Things to watch when adding records

• Name (Host) field: type the short name from the table (@, _dmarc, default._domainkey). Most panels add the domain to the end themselves; if you type the full name, the record ends up at a wrong name such as default._domainkey.examplecompany.com.examplecompany.com.
• Cloudflare: turn off the orange cloud (DNS only) on all CNAME records (autoconfig, autodiscover, imap, smtp, mail). Mail records do not work through the proxy.
• SRV records: if your panel has separate fields, enter priority 0, weight 1, the port (443, 993, 465 or 587) and target mx1.gyrohosting.com. Type the short name such as _imaps._tcp in the name field.
• TXT values: paste them without quotes. The DKIM value is long; some panels split values longer than 255 characters on their own, which is normal.
• Old MX records: delete all old MX records. Only our MX record should remain; otherwise some mail goes to the old server.

Merging SPF

A domain can have only one SPF record. If you already have a TXT record starting with v=spf1, do not create a second one; add include:_spf.gyrohosting.com to the existing record.

Example: if your website sends form email from a server at 203.0.113.10:

v=spf1 mx ip4:203.0.113.10 include:_spf.gyrohosting.com ~all

Remove your old provider's include: value after the migration is finished and MX has changed.

Tightening DMARC over time

The client area suggests DMARC with p=none: no mail is rejected, it is only monitored. After a few weeks, once you are sure every service that sends mail for you passes SPF and DKIM, you can move to p=quarantine and then p=reject. There is no need to rush this.

5. Troubleshooting

6. How long does it take?

A DNS change can take from a few minutes to a few hours to be visible everywhere. This depends on the record's old cache time (TTL) and cannot be sped up on our side. Our check asks your domain's name server directly, so you usually see "Correct" before the rest of the internet sees the new MX.

7. Frequently asked questions