By Symba
According to the standards in section 3.1.1, you should create both a TXT and SPF Record types with identical content. Having one of these record types make you compliant, but it’s better to publish both, if you are able.
In DNS I don’t have a SPF field… is there a way to do this ?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
What standards? By you mentioning section 3.1.1 I assume that you are referring to RFC4408? We now have the Standard Track RFC7208, which obsoletes RFC4408.
Let me quote the beginning of http://tools.ietf.org/html/rfc7208#section-3.1
“SPF records MUST be published as a DNS TXT (type 16) Resource Record (RR) [RFC1035] only.”
Also, if you take a look at some of the big players, such as gmail.com, yahoo.com and fastmail.com, you’ll see that all of them only use the TXT records for their SPF info.
In short, not being able to create records of the SPF type is a feature, not a bug.
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.