hangText=NOTE: The use of wildcard TXT records in the
DNS will produce a response to a DKIM query that is
unlikely to be valid DKIM key record. This problem
applies to many other types of queries, and client
software that processes DNS responses needs to take this
On 10/25/10 5:11 PM, John R. Levine wrote:
Forgive me if I repeat myself, but I still don't see anything wrong
with this:
*._domainkey.example.com IN TXT v=DKIM1; p=; n=revoked
I'm trying to figure out the clearest way to say that wildcards for
key records within the _domainkey subtree
On 10/25/2010 10:26 AM, Eliot Lear wrote:
Won't be visible because you are querying what amounts to a
specific application through the use of the label.
...
There should be no other existing records, and if so, they're
there to override the wildcard.
Right.
The underscore naming
On Oct 25, 2010, at 8:11 AM, John R. Levine wrote:
hangText=NOTE: The use of wildcard TXT records in the
DNS will produce a response to a DKIM query that is
unlikely to be valid DKIM key record. This problem
applies to many other types of queries, and client
software that
Forgive me if I repeat myself, but I still don't see anything wrong with this:
*._domainkey.example.com IN TXT v=DKIM1; p=; n=revoked
Do you have an actual use case for that sort of thing, or is it just an
example to poke at the thou shalt not wildcard wording?
That example above revokes
John,
The reported issue was about *mixed* TXT usage caused by wildcards.
And it amounted to a large Domain Hosting vendor ONLY offering this
for spf:
*.example.com IN TXT v=spf1 ..
And that created mixed query results after adding DKIM related TXT
records.
The proposed
