Mark wrote:
Dig uses ‘.’ when printing out unknown EDNS options when the value
is not printable ASCII.
I played e little with dig and Extended DNS Errors (RFC8914) and it
turned out to be perfectly possible to add UTF-8 encoded strings in there:
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; EDE: 4 (Forged Answer): (キルロイはここにいた DNS4ALL frontend fiddled around
with this reply -
Is that because it it not an 'unknown' EDNS option ?
Perhaps also because RFC8914 says: EXTRA-TEXT: a variable-length,
UTF-8-encoded [RFC5198] text field.
Infourls in RESINFO RRtype records (RFC9606) on the other hand, look
like this:
;; ANSWER SECTION:
resinfo.testdns.nl. 0 IN RESINFO "qnamemin" "temp-dnssecval"
"infourl=https://\228\190\139\229\173\144.\207\128\206\177\207\129\206\172\206\180\206\181\206\185\206\179\206\188\206\177/\227\130\173\227\131\171\227\131\173\227\130\164\227\129\175\227\129\147\227\129\147\227\129\171\227\129\132\227\129\159";
Probably because section 4 says: "The resolver information record uses
the same format as DNS TXT records."
Both RFCs have a disclaimer that the information is intended for human
consumption, not automated parsing.
Interesting stuff. ;-)
--
Marco
_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]
