Expose comments in dig result embed

[MattIPv4]

When a DNS lookup is run, some resolvers (such as 1.1.1.1) return comments with additional information, such as warning about DNSSEC failures. We should expose these comments to the end user in the embed generated by the dig command.

curl -H "Accept: application/dns-json" https://cloudflare-dns.com/dns-query\?name\=yumi.dev

{"Status":2,"TC":false,"RD":true,"RA":true,"AD":false,"CD":false,"Question":[{"name":"yumi.dev","type":1}],"Comment":["EDE(9): DNSKEY Missing (no SEP matching the DS found for yumi.dev.)"]}

curl -H "Accept: application/dns-json" https://cloudflare-dns.com/dns-query\?name\=maven.yumi.dev\&cd\=true

{"Status":0,"TC":false,"RD":true,"RA":true,"AD":false,"CD":true,"Question":[{"name":"maven.yumi.dev","type":1}],"Answer":[{"name":"maven.yumi.dev","type":1,"TTL":300,"data":"104.21.73.112"},{"name":"maven.yumi.dev","type":1,"TTL":300,"data":"172.67.162.66"}],"Comment":["EDE(9): DNSKEY Missing (no SEP matching the DS found for yumi.dev.)"]}

curl -H "Accept: application/dns-json" https://dns.google/resolve\?name\=yumi.dev

{"Status":2,"TC":false,"RD":true,"RA":true,"AD":false,"CD":false,"Question":[{"name":"yumi.dev.","type":1}],"Comment":"DNSSEC validation failure. Check http://dnsviz.net/d/yumi.dev/dnssec/ and http://dnssec-debugger.verisignlabs.com/yumi.dev for errors"}

Note that Comment may be a string, or an array of strings, so the logic will need to handle both. Note that comments may be included even when a lookup is successful, such as if there was a DNSSEC error, but checking was disabled.

[itsMathew]

Hey, is this still open? Would be very happy to fix this

[MattIPv4]

Yeh, go for it

[itsMathew]

I tried to get the app running, but is the v2 branch working? I managed to add the interaction endpoint, but now my logs just show
[wrangler:inf] POST / 404 Not Found whenever i run a slash cmd
Could you please guide me through this?

[MattIPv4]

What route have you configured in Discord for interactions? It should be https://hostname/interactions.

[itsMathew]

Ah, yeah that was the problem. Thank you, I'll post a PR soon.

[itsMathew]

So I have handled the string type for comment (The comment is in the footer of the embed)

I tried to replicate an array of strings coming through, but couldn't get it to work..
This is what I tried

but this never seems to return any comment, would be great if you could guide me on how to replicate it..
Also what would be an ideal place to place this array of strings?

[MattIPv4]

Ah, looks like that domain not longer has DNSSEC issues so you're not getting back the comments I originally showed in the issue.

You can use dnssec-failed.org which should give similar results.

curl -H "Accept: application/dns-json" https://dns.google/resolve\?name\=dnssec-failed.org

{"Status":2,"TC":false,"RD":true,"RA":true,"AD":false,"CD":false,"Question":[{"name":"dnssec-failed.org.","type":1}],"Comment":"DNSSEC validation failure. Check http://dnsviz.net/d/dnssec-failed.org/dnssec/ and http://dnssec-debugger.verisignlabs.com/dnssec-failed.org for errors","extended_dns_errors":[{"info_code":9,"extra_text":"No DNSKEY matches DS RRs of dnssec-failed.org"}]}

curl -H "Accept: application/dns-json" https://cloudflare-dns.com/dns-query\?name\=dnssec-failed.org

{"Status":2,"TC":false,"RD":true,"RA":true,"AD":false,"CD":false,"Question":[{"name":"dnssec-failed.org","type":1}],"Comment":["EDE(9): DNSKEY Missing no SEP matching the DS found for dnssec-failed.org."]}

curl -H "Accept: application/dns-json" https://cloudflare-dns.com/dns-query\?name\=dnssec-failed.org\&cd\=true

{"Status":0,"TC":false,"RD":true,"RA":true,"AD":false,"CD":true,"Question":[{"name":"dnssec-failed.org","type":1}],"Answer":[{"name":"dnssec-failed.org","type":1,"TTL":300,"data":"96.99.227.255"}],"Comment":["EDE(9): DNSKEY Missing no SEP matching the DS found for dnssec-failed.org."]}