Difference between revisions of "DNS Info"

From TheBestLinux.com
Jump to navigation Jump to search
Line 17: Line 17:
 
<br />
 
<br />
  
Check and Test Your MX Record Setup/Configuration from the command line:
+
Check and test your MX record setup/configuration from the command line on your new email server:
 
<br />
 
<br />
 
<pre style="color:blue">
 
<pre style="color:blue">
Line 23: Line 23:
 
</pre>
 
</pre>
 
<br />
 
<br />
If the result of this command is the IP address of your server, you're good.<br />  
+
If the result of this command is the IP address of your server, you are good to go!.<br />  
If not, check your MX records in your domain DNS zone; and make sure you have waited long enough for the changes to spread.<br />  
+
If it is not, check the MX records of your domain DNS zone.  Also, be sure you have waited long enough for the changes to spread through the internet.<br />  
 
This can take up to 24 hours. Also make sure your /etc/resolv.conf file is listing valid DNS servers.
 
This can take up to 24 hours. Also make sure your /etc/resolv.conf file is listing valid DNS servers.

Revision as of 01:24, 26 September 2014

RCModelHelis.com DNS Info for GoDaddy.com DNS Server Setup Configuration

Steps to setup the Email MX DNS record allowing mail to flow to the server: (Using My New VM Host vm1.rcmodelhelis.com)

For all 3 steps below, set TTL(Time To Live) to 600 seconds
and DO NOT include the quotes in the examples:

  • Create DNS "A" Redord "vm1" which points to IP "198.56.248.58"
  • Create DNS "CName" Alias Redord "mail" which points to "vm1.rcmodelhelis.com"
  • Create DNS "MX" Record "@" which points to "mail.rcmodelhelis.com" with Highest Priority set to "0" (Lower number = higher priority)

    Save all DNS redords for changes to take effect, which is usually instant from past experience with the above examples. Others may take longer.

    Check and test your MX record setup/configuration from the command line on your new email server:
    dig +short A $(dig +short MX example.com | head -1 | cut -d' ' -f2)
    


    If the result of this command is the IP address of your server, you are good to go!.
    If it is not, check the MX records of your domain DNS zone. Also, be sure you have waited long enough for the changes to spread through the internet.
    This can take up to 24 hours. Also make sure your /etc/resolv.conf file is listing valid DNS servers.