5

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

4 replies

null
    • FayneAldan
    • 8 mths ago
    • Reported - view

    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)

    • Gordon_Thomson
    • 6 mths ago
    • Reported - view

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

    • Timothy_Rogers
    • 3 mths ago
    • Reported - view

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

    • Shake
    • 1 mth ago
    • Reported - view

    I can't resolve Handshake domains using NextDNS

Content aside

  • 5 Likes
  • 1 mth agoLast active
  • 4Replies
  • 140Views
  • 6 Following