Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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

This question already has an answer here:

I've inherited a TinyDNS configuration that have following entries for SPF:

' ip4\072x.x.x.3 ip4\07231.130.96.103 ptr\ +mx a -all:3600
' ip4\072x.x.x.3 ip4\072x.x.x.103 ptr\ +mx a -all:3600
' ip4\072x.x.x.3 ip4\072x.x.x.103 ptr\ +mx a -all:3600

This is the result from

SPF record lookup and validation for:

SPF records are primarily published in DNS as TXT records.

The TXT records found for your domain are:
v=spf1 ip4:x.x.x.3 ip4:x.x.x.103 +mx a -all 

SPF records should also be published in DNS as type SPF records.
No type SPF records found.

Checking to see if there is a valid SPF record. 

Found v=spf1 record for 
v=spf1 ip4:x.x.x.3 ip4:x.x.x.103 +mx a -all 

SPF record passed validation test with pySPF (Python SPF library)!

I'm struggling with this from yesterday and cant figure it why this validator returns No type SPF records found. I see in BIND we cand define SPF type record with IN SPF "v=spf1 a -all", but in TinyDNS we only have TXT records that we set for SPF, maybe this is a problem?

share|improve this question

marked as duplicate by MichelZ, MadHatter, mdpc, Jenny D, dawud Apr 26 '14 at 7:59

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

And yes, that last line describes the problem exactly. Make a record of type SPF that exactly mirrors the record of type TXT. – MadHatter Apr 25 '14 at 20:35

The SPF RR Type is not available in all DNS server implementations, which is why the RFCs allow consumers to fallback to TXT record evaluation.

If TinyDNS has no SPF record types, your configuration is just fine.

share|improve this answer

You can manually enter a spf (type 99) record in tinydns format. The trick is that you have to include the length of the data in octal format.

You can use the wizard at to generate a generic txt (type 12) record, then just change the 12 to 99 and you have a SPF record.

Here is an example:\041v=spf1 ip4\072192.168.001.01/30 -all:3600

The first : means a generic record for The 99 specifies record type 99. The \041 is octal for 33, the number of characters in the data. \072 is octal for :, count all encoded octal characters as 1 char.

Credit goes to Robert Thille for his post -

share|improve this answer

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