Unable to resolve handshake domain
I have enabled the web3 option but cannot resolve handshake domains (e.g. http://namebase/ ) However, I can resolve ENS domains like vitalik.eth
7 replies
-
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
Content aside
-
6
Likes
- 9 days agoLast active
- 7Replies
- 325Views
-
9
Following