On Mon 27/Mar/2023 18:25:24 +0200 Brad Beyenhof via mailop wrote:
On 3/27/23, 9:18 AM, "mailop on behalf of Heiko Schlittermann via mailop"
<mailop-boun...@mailop.org <mailto:mailop-boun...@mailop.org> on behalf of mailop@mailop.org
<mailto:mailop@mailop.org>> wrote:
Lena--- via mailop <mailop@mailop.org <mailto:mailop@mailop.org>> (Mo 27 Mär
2023 17:40:29 CEST):
If the DNS name xxx._domainkey.example.com exists, then
_domainkey.example.com exists too.
dig 3._domainkey.lena.kiev.ua txt
3._domainkey.lena.kiev.ua. 66633 IN TXT "v=DKIM1; p=MIGfMA0GCSqGSIb...
dig _domainkey.lena.kiev.ua txt
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 57410
Reading https://www.rfc-editor.org/rfc/rfc8020#section-3.1
<https://www.rfc-editor.org/rfc/rfc8020#section-3.1>
this should not happen, shouldn't it?
It's possible that `3._domainkey` is a dotted record in the DNS zone for
`lena.kiev.ua`, and `_domainkey.lena.kiev.ua` isn't set up as its own zone.
Isn't that the usual way to do it? I certainly didn't create a new zone for
_domainkey. Yet, I have (using bind):
; <<>> DiG 9.16.37-Debian <<>> _domainkey.tana.it any
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18450
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
Best
Ale
--
_______________________________________________
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop
