Subdomain gateway DNS lookup failure

[Dwiib]

Describe the bug

Loading a static site such as http://ipfs.dappnode:8080/ipfs/bafybeiawq7pbt4krnopfmcvymvp2uz4ohibd5p7ugskkybvdmwa2v7evpy (vitalik.eth's content hash) redirects to cid.ipfs/ipns.ipfs.dappnode:8080 which is correct for IPFS subdomain support, but results in a DNS lookup failure.

Replacing ipfs.dappnode with the container IP works as expected

To Reproduce

• Access http://ipfs.dappnode:8080/ipfs/bafybeiawq7pbt4krnopfmcvymvp2uz4ohibd5p7ugskkybvdmwa2v7evpy via a web browser -> failure
• Access http://$ipfs_container_IP:8080/ipfs/bafybeiawq7pbt4krnopfmcvymvp2uz4ohibd5p7ugskkybvdmwa2v7evpy via web browser -> success
• dig bafybeiawq7pbt4krnopfmcvymvp2uz4ohibd5p7ugskkybvdmwa2v7evpy.ipfs.ipfs.dappnode shows empty answer section
• dig ipfs.dappnode correctly responds with an A record to $ipfs_container_IP

Expected behavior

*.ipfs.dappnode should resolve to the container IP, and ipfs.ipfs.dappnode/ipns.ipfs.dappnode should function correctly as subdomain gateways. Note: IPFS redirects do not work with the more common gw.tld/ipfs/cid format, so subdomain gateways should be preferred. https://docs.ipfs.tech/how-to/websites-on-ipfs/redirects-and-custom-404s/

DAppNode version:

Core DAppNode Packages versions

    bind.dnp.dappnode.eth: 0.2.11
    core.dnp.dappnode.eth: 0.2.92
    dappmanager.dnp.dappnode.eth: 0.2.86, commit: ad99085d
    https.dnp.dappnode.eth: 0.2.1
    ipfs.dnp.dappnode.eth: 0.2.22
    wifi.dnp.dappnode.eth: 0.2.9
    wireguard.dnp.dappnode.eth: 0.1.3

System info

    dockerComposeVersion: 2.24.7
    dockerServerVersion: 25.0.4
    dockerCliVersion: 25.0.4
    os: debian
    versionCodename: bookworm
    architecture: amd64
    kernel: 6.1.0-18-amd64
    Disk usage: 29%

• OS: Debian via unattended installer
• Browser: Firefox

Additional context

[3alpha]

Hey, we have fix in the works, but in the meantime you can use built in ENS resolver and access Vitalik's blog using: http://vitalik.eth while connected to you DAppNode, of course.