add an SPF record to the DNS template
SPF information is so far entered through the TXT record. Adding the emerging new SPF record would make sense.
Anonymous
shared this idea
Thank you for your input! We do not plan for adding support of SPF record as a resource record (RR).
[...] 3.1. DNS Resource Records SPF records MUST be published as a DNS TXT (type 16) Resource Record (RR) [RFC1035] only. The character content of the record is encoded as [US-ASCII]. Use of alternative DNS RR types was supported in SPF's experimental phase but has been discontinued. [...]
Additional information can be obtained by link https://tools.ietf.org/html/rfc7208#section-3.1
— AY
-
Madalin Ignisca
commented
SPF record has been deprecated to the same syntax but with TXT record. Just keep with the news in the Email standards ;)
-
Anonymous
commented
The SPF (type 99) dns resource record will be the successor of the SPF-TXT entry.
So why would we only enter TXT records while there is a newer one
-
Anonymous
commented
according to openspf:
http://www.openspf.org/Community/SPFv3-SPF-RR-exclusiveSPFv3 will use exclusively the SPF RR (type 99).
RFC 4408 used the TXT RR because the newer record type was not widely available. After several years, most DNS software as been modified introducing the SPF type
why wouldn't Plesk Parallels allows us to use it.
-
Tozz
commented
There is no specific reason for SPF records, as SPF RR's are deprecated. However, there are other RR's that are not available on Plesk but are available in BIND. There is no reason why these RR's could not be implemented simply by allowing them in the Plesk GUI.
-
Tozz
commented
I voted for this feature request, but I feel it should not be limited to SPF RR record. Plesk currently only implements a subset of all available RR's, but there is no reason why Plesk should limit the available RR's. As Plesk uses Bind, it would be a piece of cake to allow other RR types.