Unable to resolve handshake domain

Same issue here. ENS and Unstoppable Domains work, but Handshake doesn't.

> Resolve-DnsName -Server 45.90.28.61 -Name namebase. -Type A
Resolve-DnsName: namebase. : DNS name does not exist.

> Resolve-DnsName -Server 45.90.28.61 -Name vitalik.eth -Type A

Name                                           Type   TTL   Section    IPAddress
----                                           ----   ---   -------    ---------
vitalik.eth                                    A      300   Answer     104.17.96.13
vitalik.eth                                    A      300   Answer     104.17.64.14

> Resolve-DnsName -Server 45.90.28.61 -Name ipfs-fps.crypto -Type A

Name                                           Type   TTL   Section    IPAddress
----                                           ----   ---   -------    ---------
ipfs-fps.crypto                                A      57    Answer     104.17.64.14
ipfs-fps.crypto                                A      57    Answer     104.17.96.13

(45.90.28.61 is NextDNS's IPv4 for Linked IP)

I'm having the same issue, unable to resolve handshake TLDs.

I am also experiencing this issue, Handshake domains are not resolving.

I can't resolve Handshake domains using NextDNS

Looks like this is still the case, no handshake domains resolve. Queries for any domain return 2 IPs (3.141.96.53 and 3.20.137.44) regardless of there being a valid site or not.

Is there anyone we need to contact (NextDNS, Namebase, Namecheap, etc.) to get this working again?

Can we get someone from NextDNS to look into this?

Facing this issue too

Same issue here. Handshake domains aren't resolving when using NextDNS, but do resolve if I try an nslookup with the hdns.io servers (103.196.38.38 / 103.196.38.39).

Can we get a rational for why this is not working?

This has been an ongoing issue for well over 2 years now, it would be great if it could be fixed as I'd love to be able to easily use my handshake domains. Surely it's not even a hard fix.

Still broken. This was one of the original reasons I signed up for NextDNS. If it's an offered feature it should be in working order.

I guess it might be related to security, like... it is not good to allow any Handshake domain that might be used to mislead an user into clicking?
But then I got ask why not allow per account whitelist of handshake domains? So we can actually use the feature?

Still waiting for a fix for this. This issue wouldn't be due to a security concern, any non-web3 domain can also point to a malicious site. The simple fact is:
There is a toggle in the profile settings to enable web3 domains. Handshake is specifically listed in the toggle description. It does not work at all.
This is an advertised feature that is currently unusable, and there has been no communication at all regarding this issue. Some people, such as myself, specifically chose to use NextDNS initially and pay for the service to allow for easy access to web3 domains, along with the other security features, rather than use an alternative such as Control D or self-host PiHole or Adguard Home (which I was originally doing, and had no issue with).
It would be nice if someone that worked at NextDNS would at least chime in at all regarding this issue @nextdns @olivier @romain