# DNSSEC (ed448)

**URL:** <https://discourse.pi-hole.net/t/dnssec-ed448/58924>\
**Category:** Help\
**Created:** [November 2, 2022, 8:47am UTC](https://discourse.pi-hole.net/t/dnssec-ed448/58924 "2022-11-02T08:47:11Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![jpgpi250](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jpgpi250/32/286_2.png) [@jpgpi250](https://discourse.pi-hole.net/u/jpgpi250)\
**Post date:** [November 2, 2022, 4:21pm UTC](https://discourse.pi-hole.net/t/dnssec-ed448/58924/4 "2022-11-02T16:21:57Z")

</div>

This has been discussed in 2018, see [here](https://discourse.pi-hole.net/t/dnssec-test-fails/9586/2). You need to run the test, described in the topic), as you can see, in the topic (screenshot), ED448 wasn't really supported at that time.

Things have changed, the current situation, on my system, using pihole-FTL version dnsmasq vDev-14cffae (on request of DL6ER) + compiled unbound (see github), is:

 ![image](https://discourse.pi-hole.net/uploads/default/original/3X/9/e/9eea35ae62662c4c377a73d7284372d11117fe45.png)

It looks like the domain has a perfect score, see [here](https://dnssec-debugger.verisignlabs.com/ed448.no), so if you can't resolve the domain, either dnsmasq (= piholeFTL) or your upstream resolver doesn't handle the DNSSEC records as expected. **Note that I use DNSSEC on unbound (disabled on pihole)**

I get

```auto
dig ed448.no

; <<>> DiG 9.16.33-Raspbian <<>> ed448.no
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27031
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;ed448.no. IN A

;; ANSWER SECTION:
ed448.no. 3369 IN A 194.63.248.47

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Nov 02 16:55:13 CET 2022
;; MSG SIZE rcvd: 53

```

---

_[View the full topic](https://discourse.pi-hole.net/t/dnssec-ed448/58924)._