Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

My boss asked me to set up Google Apps for a client and basically I have done everything including setting up MX records in DirectAdmin and re-creating the email accounts in Google Apps.

I also sent a few test emails to ensure that it actually works and it seems fine.

But then I discovered this article talking about changing the SPF record for the domain.

After reading the introduction I think it would be better for me to change the SPF record according to this article.

So I logged in to the DirectAdmin and navigated to the DNS management, and then I found that there's already a TXT SPF record there:

v=spf1 a mx -all

And it looks like it's already including, but according to the article it should be:

rather than:

I dare not to change it before I understand what this record actually means.

What would you do with this record if you were me?

share|improve this question

closed as off-topic by HopelessN00b Apr 3 '15 at 17:07

  • This question does not appear to be about server, networking, or related infrastructure administration within the scope defined in the help center.
If this question can be reworded to fit the rules in the help center, please edit the question.

up vote 3 down vote accepted

The include option in an SPF record simply says that you want to include someone else's policy in addition to what's defined in your own record.

If we look at the SPF record for

dig -ttxt

; <<>> DiG 9.6.0-APPLE-P2 <<>> -ttxt
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52705
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;         IN  TXT

;; ANSWER SECTION:      255 IN  TXT "v=spf1"

;; Query time: 18 msec
;; WHEN: Sat Jan  8 14:31:43 2011
;; MSG SIZE  rcvd: 71

We see that it simply redirects to, so you can change it or not, and it will make no difference. I would probably go ahead and change it, in case Google ever turn off the redirect.

(The instructions for setting up SPF for Google Apps say that you should include

But that also just redirects to

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.