Gordon Fecyk wrote:
No one's brought up RFC 1464 yet, which describes how to store
unique and arbitrary information in TXT records in DNS. SPF does
this, DMP does this. It avoids the TXT record collision problem
by describing a unique attribute name along with a value for the
attribute.
I don't think that's the main concern. I believe that the issue is that
there is no way to request 'all TXT records which attribute equals "v"
and value begins with "spf1"'. Unless I missed something the way to
check for specific records is to query for all TXT records then parse
which ones are relevant, which is sub-optimal. I could live with it, but
apparently many people can't.
How does ISC dhcpd store its host information in the TXT
records? And how does it tell the difference between
its own records and something else's? Doesn't it use a
token like RFC 3309 or an attribute format like RFC 1464?
That would be interesting to know indeed.
Michel.