I am trying to setup multiple SPF records per the suggestion of the SPF Wizard (bottom of the page: http://old.openspf.org/wizard.html?mydomain=mac-developer-network.com).

The first is for the domain mac-developer-network.com. All the other domains have an SPF record that redirects to the one below and appear to be working fine.

v=spf1 a mx ptr:server.mac-developer-network.com a:tetburycc.com a:macdevnet.com a:mac-developer-network.com a:latenightcocoa.com a:developersagainstpoverty.org a:macdevelopernetwork.com a:scottysblog.com a:petra-fellowship.org a:nsconference.com a:mamooba.com ~all

The wizard also indicated I should setup a record for server.mac-developer-network.com which is the actual MX

server.mac-developer-network.com. IN TXT "v=spf1 a -all"

However when I try and do it in the DNS management for the mac-developer-network.com domain it doesn't work. It simply isn't detected. I've tried looking with dig, nslookup & http://www.mxtoolbox.com

I opened a support case about it (I didn't think of the forums) and they suggested setting up a seperate DNS zone for server.mac-developer-network.com. Is that really the way to go? It seems a little extreme for a TXT record.

SPF tests are passing at the moment, though the HELO test has a result of none:

SPF Tests:
Mail-From Result="pass": Mail From="postmaster@mac-developer-network.com"
HELO name="server.mac-developer-network.com" HELO Result="none" Remote
IP="178.79.134.244"

Many thanks

-- MINOR Update --

I host my own servers (tarasis.net) DNS on dyndns on and there I have two TXT entries one for tarasis.net & one for daffy.tarasis.net and both are found correctly. Though even then mailing "spf-test@openspf.org" results in a HELO Result="none" BUT the result of mailing check-auth@verifier.port25.com from tarasis.net suggests the its working correctly I see SPF_HELO_PASS in the SpamAssassin results where mails from mac-developer-network.com doesn't include that result.

I guess though this is wandering off the original topic.

--- UPDATE ---

I had a final response from my support ticket that sorted the problem out without resorting to a second DNS zone.

Apparently the first TXT record should have been created with a Name of "" and the second with a name of "server" [note the missing period, apparently "The Linode DNS manager will automatically append the name of the zone to any txt records that you create"]

Both are looking OK from here:

$ dig mac-developer-network.com txt +short
"v=spf1 a mx a:tetburycc.com a:macdevnet.com a:mac-developer-network.com a:latenightcocoa.com a:developersagainstpoverty.org a:macdevelopernetwork.com a:scottysblog.com a:petra-fellowship.org a:nsconference.com a:mamooba.com ip4:178.79.134.244 ptr:server.m" "ac-developer-network.com mx:server.mac-developer-network.com -all"
$ dig server.mac-developer-network.com txt +short
"v=spf1 a -all"

It's possible that your local nameserver has their non-existence cached, especially if you tried to check the records before they existed.

_________________

/* TODO: need to add signature to posts */

Thanks for checking, I had a reply from support about 10 minutes before you posted that did the trick.

Apparently I had to set the first TXT record with a Name of "" and the second TXT record had to have a name of "server" without the period.

I had to go sort out lunch before I could updated the forum :/

My first rule of DNS-related stuff: make a change, eat lunch, then make sure it worked. So, you did the right thing by taking care of lunch!

_________________

/* TODO: need to add signature to posts */