Пропускане към основното съдържание

MX record

MX Records Overview

An MX (mail exchange) record is an entry in your DNS zone file which specifies a mail server to handle a domain's email. You must configure an MX record to receive email to your domain.

 If you are using Kerio Connect as an internal email system, with no communication outside of your domain, it's not necessary to configure an MX record for your domain. You may configure any domain in Kerio Connect, as it does not perform any DNS validation of its local domain names.  

Setting Up an MX Record

1. To relay email outside of your locally configured domains, ensure that the underlying operating system properly resolves domain names. This means that a valid domain name server must be configured in the TCP/IP settings of the host operating system.
2. Configure the MX record on the authoritative name server for your domain:
In most cases, the authoritative name server is the DNS servers managed by your domain registrar – for example, Godaddy or Network Solutions.
These domain registrars usually provide additional services, including DNS hosting. In this case, you will use a web-based DNS configuration utility to configure your MX record.
Here are some additional resources for configuring an MX record for Godaddy and Network Solutions.

- link
- link

 Since most DNS servers store its information in a cache for a certain period of time, it might take up to 24 hours for the change to get propagated over the internet to DNS servers where the record is stored. Email delivery can be pointed to the secondary email server in the MX record list until the primary server DNS name is changed.  

3. Check if a DNS server applied the MX record changes by using nslookup command-line tool:

 mac-mini: username$ nslookup  
 > server server:  
 > set q=MX  
 > kerio.com  

Checking an MX Record

You can check a DNS MX record using an online test tool (e.g. http://mxtoolbox.com/) or by using nslookup command-line tool.
In the following example, three servers can receive emails for the kerio.com email domain. The lowest number means the highest server preference. In this example the primary MX server (the server with highest preference) is mx1.kerio.com:

Additional Resources

. http://en.wikipedia.org/wiki/Mx_record - A mail exchanger record (MX record) is a type of resource record in the Domain Name System that specifies a mail server responsible for accepting email messages on behalf of a recipient's domain, and a preference value used to prioritize mail delivery if multiple mail servers are available. The set of MX records of a domain name specifies how email should be routed with the Simple Mail Transfer Protocol.
. http://www.icann.org/registrar-reports/accredited-list.html - The following companies have been accredited by ICANN to act as registrars in one or more top level domains.
. http://www.internic.net/regist.html - The following companies have been accredited by ICANN to act as registrars in one or more top level domains.


If you have your domain name pointed elsewhere, but you wish to have your mail handled by your web hosting provider (e.g. domain.com), you can easily achieve this by pointing your domain's MX (Mail eXchange) record to your host.

To point your mail service to us, you should change your MX record of your domain to point to your server's hostname. For example, if your account is hosted on domainXXX.com, then you should change your MX record to: domainXXX.com.

Select the domain name for which you want to alter the MX record from the drop down menu.

Now, the default MX records configuration will be loaded.
Important! The SpamExperts service is available only on our Shared hosting solutions. If you're hosted on our Cloud VPS or Dedicated servers, that option is not available for you by default.

Currently the domain clients benefit from the SpamExperts spam protection solution and the default MX records resolve to the corresponding servers cluster.

If changed, the default configuration can be restored by clicking on the Revert Default button. Clicking on the Set Google MX button automatically configures the required MX records for Google.

Mind that after the MX record is set, you need to wait up to 48 hours for the DNS change to propagate.


Публикуване на коментар

Popular Posts

DVWA - Brute Force (High Level) - Anti-CSRF Tokens

This is the final "how to" guide which brute focuses Damn Vulnerable Web Application (DVWA), this time on the high security level. It is an expansion from the "low" level (which is a straightforward HTTP GET form attack). The main login screen shares similar issues (brute force-able and with anti-CSRF tokens). The only other posting is the "medium" security level post (which deals with timing issues). For the final time, let's pretend we do not know any credentials for DVWA.... Let's play dumb and brute force DVWA... once and for all! TL;DR: Quick copy/paste 1: CSRF=$(curl -s -c dvwa.cookie "" | awk -F 'value=' '/user_token/ {print $2}' | cut -d "'" -f2) 2: SESSIONID=$(grep PHPSESSID dvwa.cookie | cut -d $'\t' -f7) 3: curl -s -b dvwa.cookie -d "username=admin&password=password&user_token=${CSRF}&Login=Login" "192.168.1

Facebook structure_intentional uncertainty

+ Server: No banner retrieved + X-XSS-Protection header has been set to disable XSS Protection. There is unlikely to be a good reason for this. + Uncommon header 'x-fb-debug' found, with contents: SA17Z/1jGOMUff7U39k20M0c/6sSZAD/Jvv00FPyIR603jOZAx91mrwQ5WVjhkAOm0FI683ditjc0KXc2o+5DQ== + Entry '/album.php' in robots.txt returned a non-forbidden or redirect HTTP code (200) + Entry '/checkpoint/' in robots.txt returned a non-forbidden or redirect HTTP code (302) + Entry '/contact_importer/' in robots.txt returned a non-forbidden or redirect HTTP code (200) + Entry '/file_download.php' in robots.txt returned a non-forbidden or redirect HTTP code (200) + Entry '/live/' in robots.txt returned a non-forbidden or redirect HTTP code (302) + Entry '/moments_app/' in robots.txt returned a non-forbidden or redirect HTTP code (302) + Entry '/p.php' in robots.txt returned a non-forbidden or redi

List of TCP and UDP port numbers

This is a list of Internet socket port numbers used by protocols of the transport layer of the Internet Protocol Suite for the establishment of host-to-host connectivity. Originally, port numbers were used by the Network Control Program (NCP) in the ARPANET for which two ports were required for half-duplex transmission. Later, the Transmission Control Protocol (TCP) and the User Datagram Protocol (UDP) needed only one port for full-duplex, bidirectional traffic. The even-numbered ports were not used, and this resulted in some even numbers in the well-known port number range being unassigned. The Stream Control Transmission Protocol (SCTP) and the Datagram Congestion Control Protocol (DCCP) also use port numbers. They usually use port numbers that match the services of the corresponding TCP or UDP implementation, if they exist. The Internet Assigned Numbers Authority (IANA) is responsible for maintaining the official assignments of port numbers for specific uses. However, many unoff