DNS records are not verifying

What to do when a record on your domain shows Missing, Pending, Conflict or Error.

Updated

Open Admin console → Domains, open the domain and choose Check. Find the records that are not OK, then use the matching section below.

Missing

The record does not exist yet.

  1. Tick it in the list of changes.
  2. Choose Apply selected.
  3. Wait a few minutes and choose Check again.

Pending

The record is in place, and we are waiting for it to be confirmed. Sending records are confirmed by our mail infrastructure, which checks DNS by itself.

  • Wait. Most records are confirmed within minutes. Some take up to a day, because DNS answers are cached.
  • Choose Check again later. We also check every domain once a day.
  • Still pending after 24 hours? Write to support@onebitmail.com.

Conflict

Something already in your DNS gets in the way.

RecordUsual conflictWhat to do
MXAnother provider receives your mail today.See Move your mail from another provider.
SPFThe domain has two SPF records (two TXT records starting with v=spf1).Merge them into one, by hand, with whoever manages your DNS. Then check again.
Any recordA record with the same name exists with a different value.Review the update in the list of changes. Tick it if the new value is right.

Error

The record cannot be fixed automatically. The details say why. The most common one:

SPF has too many lookups. An SPF record may need at most 10 lookups. Each include: uses at least one. If adding ours would go over 10, remove include: entries of services you no longer send through, then check again.

SPF is malformed. The record has a typo, for example two all endings. Fix it by hand, then check again.

An update is not applied

Changing an existing record is never done automatically. In the list of changes, records marked Update must be ticked before you apply. Read the current and new values first.

A record was OK and now is not

We check every domain daily. If a record breaks later, for example because someone edited DNS, sending from that domain stops until it is fixed, and admins are told. Choose Check, then apply the missing or changed records again.

Sending is OK but receiving is not, or the other way round

Receiving and sending use different records. Receiving needs the MX records. Sending needs SPF, DKIM and the bounce records. Fix the side that is not OK.

Still stuck?

Write to support@onebitmail.com with the domain name and a screenshot of the check results.

Still need help?

Write to support@onebitmail.com. A person reads every message.