I am trying to troubleshoot an issue with using the eth.link gateway for ipns pinned content. I think something changed recently, and I cannot afford to update ens.domains for a new blockchain transaction every time i change content with a new ipfs pin. (and the resolution of ipns to that ipfs pin)
Is anyone else using ipns through the eth.link web gateway?
I can confirm that the ipns:// hash loads find from dweb for instance, so i think this is on the cloudflare and their handling of ipns.
Thanks for the reply. I am testing my node currently, the hash is retrievable from public gateways. Just not when I configure ipns:// as the content type with ens.domains. If you can show me another site using ipns:// for the hash content I’ll be glad to look.My fallback will be to use an ipfs:// hash instead, but then I pay to update the site each time I rev it… ipns:// was working at the beginning of the week…