Check DNS records
To avoid problems sending or receiving mail, make sure that your DNS records are configured correctly. You can do this using http://www.digwebinterface.com or any other dig utility.
Open the page http://www.digwebinterface.com.
Specify your domain name (such as
example.org
) in the Hostnames or IP addresses field.In the Type field, select MX and click Dig.
The response should look like this:
example.org. 20755 IN MX 10 mx.yandex.net.
Response | How to fix it |
---|---|
| Delete extra records, leaving only one with priority |
| Delete this record and set up a new one following the instructions. |
The response is empty. | Most likely, the record was not configured for your domain. Follow the instructions to set it up. If the record is configured but doesn't appear in the response, contact your hosting support. |
Response | How to fix it |
---|---|
| Delete extra records, leaving only one with priority |
| Delete this record and set up a new one following the instructions. |
The response is empty. | Most likely, the record was not configured for your domain. Follow the instructions to set it up. If the record is configured but doesn't appear in the response, contact your hosting support. |
Open the page http://www.digwebinterface.com.
Specify your domain name (such as
example.org
) in the Hostnames or IP addresses field.In the Type field, select TXT and click Dig.
The response should look like this:
example.org. 21600 IN TXT "v=spf1 redirect=_spf.yandex.net"
or
example.org. 21600 IN TXT "v=spf1 ip4:IP-1 ip4:IP-2 ip4:IP-3 include:_spf.yandex.net ~all"
If the server doesn't respond, the response doesn't match the request, or it contains too many records, the SPF record wasn't properly configured. Follow the instructions to set it up.
Open the page http://www.digwebinterface.com.
In the Hostnames or IP addresses field, enter the
mail._domainkey
subdomain name for your domain, for examplemail._domainkey.example.org
.In the Type field, select TXT and click Dig.
The response should look like this:
mail._domainkey.example.org. 21599 IN TXT "v=DKIM1\; k=rsa\; t=s\; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDlk+IUXTHUIumVpG1S0vwFuwO9AC2aRrJj21MLj7xvO0Brys/fDxOTaFsoVsA2/t9mcxf1kqx/bCsEvJiiOUUw5eihQefcY7xJoeruJK/o+IKU2dTO9OOPfSyqGLuQ+v/DMJRjhz73XOpkPOpPwLhQKhvBLNM2TCxPqCL0E42/7wIDAQAB"
If the server doesn't respond, the response doesn't match the request, or it contains too many records, the DKIM signature wasn't properly configured. Follow the instructions to set it up.