Folks, I really think we should use the opportunity to add a note
about DKIM adopters having potential DNS setup issues due to wildcard
SPF records.
When section 3.6.2.1, SPF was probably still growing and not wide
spread with Web-Based DNS managements from ISPs. Today, a special
"Add SPF record" option is available.
At least at one ISP/Domain Registrar (one of the original biggest), it
only allows a wildcard TXT record to cover the non-prefix SPF query.
This conflicts with added DKIM and ADSP dns records.
The section already has an INFORMATIVE OPERATIONAL NOTE advising not
to use wildcards for DKIM public keys records.
What I am suggesting is another short INFORMATIVE OPERATIONAL NOTE,
not about a tutorial on DNS management, but maybe just saying:
INFORMATIVE OPERATIONAL NOTE: Wildcard DNS records for SPF
records may conflict with DKIM TXT sub-domain TXT records.
DNS management software should not require only Wildcard SPF
entries and should allow for non-prefix SPF TXT enries.
The readers of this document will include web developers for DNS zone
file management when considering DKIM record support and having this
new informative note will guide them in not being conflictive with
DKIM TXT record lookups.
The only reason I like for people to consider this is because I got an
email today that Network Solutions isn't going to address this issue
for the customer.
So like Murray likes to admonish those for lack of compliancy and to
encourage to fix problems, having the helpful information operational
node will help "admonish" DNS management software developers to maybe
correct their current implementations.
--
HLS
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html
