Imtek
Verified User
I have been told that DirectAdmin still has support for RFC4870
(https://tools.ietf.org/html/rfc4870).
It wrongfully adds a TXT record under the _domainkey label of domain names.
For example:
_domainkey.example.nl TXT "o=~"
However, RFC4870 is outdated and replaced by RFC6376
(https://tools.ietf.org/html/rfc6376).
This RFC defines the _domainkey label as an 'empty non terminal' by
definition. The corresponding tags are now in a selector label, under
_domainkey, like in:
blah._domainkey.example.nl TXT "...."
(https://tools.ietf.org/html/rfc6376#section-3.6.2.1)
I propose that DirectAdmin removes support for RFC4870 if present or in any case I request DirectAdmin to review their current implementation and bring it up to date with current standards where applicable.
(https://tools.ietf.org/html/rfc4870).
It wrongfully adds a TXT record under the _domainkey label of domain names.
For example:
_domainkey.example.nl TXT "o=~"
However, RFC4870 is outdated and replaced by RFC6376
(https://tools.ietf.org/html/rfc6376).
This RFC defines the _domainkey label as an 'empty non terminal' by
definition. The corresponding tags are now in a selector label, under
_domainkey, like in:
blah._domainkey.example.nl TXT "...."
(https://tools.ietf.org/html/rfc6376#section-3.6.2.1)
I propose that DirectAdmin removes support for RFC4870 if present or in any case I request DirectAdmin to review their current implementation and bring it up to date with current standards where applicable.
Last edited:
