This article describes how to add an MX record to Godaddy if the DNS is hosted at Godaddy.

Create an A record for “mail”. Point the record to the primary IP where the mail will be hosted. This can be the same IP as the website or a different IP if mail in on a different server.

Now create the MX record. Replace “domain” with your actual domain name.

Allow for DNS propigation. Check the DNS at:

Amazonon DMARC (

This Google article is also helpful:

If you scroll down to the ‘Example records’ section, you’ll see a number of examples on how to write the TXT record. Here’s an example of that record: 3600 IN TXT “v=DMARC1; p=quarantine; pct=5;”

# dig +short TXT @ (IP of the server)

Other Information

Test your server for an open DNS resolver here:

Closing DNS Resolvers on Windows Server 2003/2008/2008 R2:

Windows Servers running Plesk:

Closing DNS Resolvers on Servers running Bind:

Configuring the rDNS for a linux server is easy. A windows server with plesk is a different story.


I changed the hostname in the plesk Tools and Settings.


Rebooted the system. Then sent a test email. Here is the header:

Received: from WIN-QO7M1M92HBS.home

Humm…where is the new hostname? So I did some investigation. I checked the computername in windows:


Then I checked the Mailenable settings > Services and Connectors > SMTP > properties.

SMTP Connector

So, the email received from name is a combination of the Windows computer name and the Mailenable Local domain name.

Now that I had this information, how do I give the mail server a valid hostname?

To Disable Recursive DNS in the Parallels Plesk Panel

  1. Log in to the Parallels Plesk Panel as administrator.
  2. Click Tools & Settings.
  3. From the General Settings area, click DNS Template Settings.
  4. Click DNS Recursion.Select Localnets, and then click Ok.

For Windows Servers:

  1. Log in to your  Server  through a Remote Desktop Connection.
  2. From the Start menu, click Control Panel, Administrative Tools, then DNS.
  3. In the console tree, right-click the appropriate DNS server, and then click Properties.
  4. Click the Advanced tab.
  5. Under Server options, check Disable recursion, and then click OK.
  6. In the console tree, right-click the appropriate DNS server, and then click Clear Cache.


# cd /etc
# nano named.conf

Change this line

# recursion yes;


# recursion no;


# service named restart


# nano /etc/bind/named.conf.options

Set up like this

// global options apply to external clients
options {
    recursion no;
    additional-from-auth no;
    additional-from-cache no;

view "local" in {
    // view options enable recursion only for local clients
    match-clients {;;; ::1; };
    recursion yes;
    additional-from-auth yes;
    additional-from-cache yes;

    zone "." in {
            type hint;
            file "/etc/bind/db.root";

    // put definitions for zones like "localhost" and "" here

// put definitions for real authoritative zones here.

Mail for some reason is not delivering to
Find your namservers.

#cat /etc/resolv.conf
nameserver 69.xx.xx.xx
nameserver 69.xx.xx.xx

– in this case the example is 69.xx.xx.xx

$ dig MX @69.xx.xx.xx
; <<>> DiG 9.9.2-P2-RedHat-9.9.2-3.P2.el5 <<>> MX @
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 19033 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ; IN MX ;; Query time: 2 msec ;; SERVER: ;; WHEN: Fri Jan 9 15:38:48 2015 ;; MSG SIZE rcvd: 29 [/bash] There is no result. Now Change to google nameservers. ( or ) [bash] ~]$ dig MX @ ; <<>> DiG 9.9.2-P2-RedHat-9.9.2-3.P2.el5 <<>> MX @
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33959 ;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ; IN MX ;; ANSWER SECTION: 17432 IN MX 10 17432 IN MX 10 17432 IN MX 10 17432 IN MX 10 ;; Query time: 11 msec ;; SERVER: ;; WHEN: Fri Jan 9 15:39:26 2015 ;; MSG SIZE rcvd: 128 [/bash]

Starting the DNS server fails. restarting named shows the following error:

service named restart
Stopping named: [ OK ]
Starting named:
Error in named configuration:
zone 0.0.127.IN-ADDR.ARPA/IN: loaded serial 20010622
zone loaded serial 1415397236
zone loaded serial 1415411359
zone loaded serial 1415556389

Thats the okay part
And then you see this:

zone NS '' has no address records (A or AAAA)
zone not loaded due to errors.


Add an A record for the nameserver in the zone DNS manager in plesk. The restart named.

# service named restart

Sender Policy Framework (SPF) is a method of fighting spam. As more time passes, this protocol will be used as one of the standard methods of fighting spam on the Internet. An SPF record is a TXT record that is part of a domain’s DNS zone file. The TXT record specifies a list of authorized host names/IP addresses that mail can originate from for a given domain name. Once this entry is placed within the DNS zone, no further configuration is necessary to take advantage of servers that incorporate SPF checking into their anti-spam systems. This SPF record is added the same way as a regular A, MX, or CNAME record.

v=spf1 mx a ip4: ~all

* Make sure the IP above has an A record set in the DNS zone


"v=spf1 a mx ~all"
“v=spf1 a mx ip4:IP.ADD.RE.SS ~all”

Example: IN TXT “v=spf1 a mx ip4:IP.ADD.RE.SS ~all”


When should I use one?

An SPF record is generally used when your company is trying to avoid people using your domain for SPAM. The thing you need to know when working with SurveyGizmo is making sure that if you do have an SPF record, that we are whitelisted in it. Whitelisting us will allow you to use your domain as the FROM field when using the SurveyGizmo application to send out email campaigns or send email actions.

What should I avoid?

If you don’t have an SPF record already in place, then we don’t recommend setting one up mid-campaign. Adding one will most likely not increase your deliverability in any way.

If you already have an SPF record, or are setting one up for other purposes, you’ll want to make sure you don’t set it to only allow SurveyGizmo. If you do, then you won’t be able to send out emails from any other servers.

If I have an SPF record, and need to whitelist SurveyGizmo, what should I use?

If you already have an SPF record set up on the domain you want to send emails from, then we recommend adding the following IP addresses to your SPF.


This will include our servers in your preferred server list. You can also use “”, however, the IP addresses above are more practical. If you were to use “” it would include all of our SPF records, which is excessive as we have internal SurveyGizmo IP addresses that the application doesn’t use.

How to make one

SPF – v=spf1 +a +mx +ip4: ?all

You can find more about SPF records here:
Server Status

and you can generate an SPF record here: