# ENS domain is not accessible through IPNS **URL:** \ **Category:** Protocol\ **Tags:** ipns\ **Created:** [February 4, 2023, 8:19am UTC](https://discuss.ipfs.tech/t/ens-domain-is-not-accessible-through-ipns/15936 "2023-02-04T08:19:37Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![ahmedibrahim](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/ahmedibrahim/32/7417_2.png) [@ahmedibrahim](https://discuss.ipfs.tech/u/ahmedibrahim)\ **Post date:** [February 4, 2023, 8:19am UTC](https://discuss.ipfs.tech/t/ens-domain-is-not-accessible-through-ipns/15936/1 "2023-02-04T08:19:37Z")
Hi! I am Ahmed, Software Engineer @ [Panther Protocol](https://pantherprotocol.io) On _Thu 2 Feb_, our users started reporting that they can’t access our dApp which is hosted on IPFS. The outages lasted for the whole day but started to work normally the day after (_Fri 3 Feb_) without any interventions. The Weird was that the dApp was not accessible using the IPNS link with the ENS domain (https://ipfs.io/ipns/pantherprotocol.eth/) but was working just fine using (_[https://pantherprotocol.eth.limo/](https://pantherprotocol.eth.limo/)_) or through IPFS CID directly [ipfs://bafybeicfwkwxy7g27x2rgiaa5f5bv5rupfxablc4ngqftptpns2dlpk6pm](https://ipfs.io/ipfs/bafybeicfwkwxy7g27x2rgiaa5f5bv5rupfxablc4ngqftptpns2dlpk6pm/#/) _ **It was only the IPNS link that was not working.** _ Here is a screenshot of what you would see if you opened [https://ipfs.io/ipns/pantherprotocol.eth/](https://ipfs.io/ipns/pantherprotocol.eth/) on _Thu 2 Feb_. ![image](https://us1.discourse-cdn.com/flex020/uploads/ipfs1/original/2X/7/7472760f8b0747ef6b3dbebc85c4a07387fdcbce.png) Also here is our ENS domain information [details](https://app.ens.domains/name/pantherprotocol.eth/details) _ **Was there any issue on IPFS/IPNS side that day? Or an idea about what was the root cause? Or about the possibility that this might happen again in the future?** _ Thanks! ---
**Author:** ![danieln](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/danieln/32/6408_2.png) [@danieln](https://discuss.ipfs.tech/u/danieln)\ **Post date:** [February 7, 2023, 12:59pm UTC](https://discuss.ipfs.tech/t/ens-domain-is-not-accessible-through-ipns/15936/2 "2023-02-07T12:59:13Z")
Hey @ahmedibrahim, Thanks for reporting this problem — this is a great question. This may have been a problem in the DNSLink resolution, which is how the IPFS node resolves from `pantherprotocol.eth` to a CID. > [@ahmedibrahim](#): > > The Weird was that the dApp was not accessible using the IPNS link with the ENS domain `https://ipfs.io/ipns/pantherprotocol.eth/` For reference, in Kubo, the DNS resolution for `.eth` names is done by default using the Cloudflare DNS over HTTPS for ENS names bridge: [https://github.com/ipfs/kubo/blob/b58356939e92729ab34e6c5e2615c67c7c4c1292/core/node/dns.go#L17-L18](https://github.com/ipfs/kubo/blob/b58356939e92729ab34e6c5e2615c67c7c4c1292/core/node/dns.go#L17-L18) You can test the resolution manually as follows: ```auto curl -H "accept: application/dns-json" "https://resolver.cloudflare-eth.com/dns-query?name=pantherprotocol.eth&type=TXT" ``` Which currently correctly returns `"dnslink=/ipfs/bafybeicfwkwxy7g27x2rgiaa5f5bv5rupfxablc4ngqftptpns2dlpk6pm"` However, we’ve seen problems with this in the past, e.g. [Could not resolve ENS domains · Issue #8836 · ipfs/kubo · GitHub](https://github.com/ipfs/kubo/issues/8836) but these are usually on the Cloudflare end of things. If you are running your own gateway node, you can configure Kubo to use the `eth.limo` DNS over HTTPS resolver: [https://github.com/ipfs/kubo/blob/master/docs/config.md#dns](https://github.com/ipfs/kubo/blob/master/docs/config.md#dns). Either way, `https://ipfs.io/ipns/pantherprotocol.eth/` works for me now ---
**Author:** ![ahmedibrahim](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/ahmedibrahim/32/7417_2.png) [@ahmedibrahim](https://discuss.ipfs.tech/u/ahmedibrahim)\ **Post date:** [February 9, 2023, 4:43pm UTC](https://discuss.ipfs.tech/t/ens-domain-is-not-accessible-through-ipns/15936/3 "2023-02-09T16:43:55Z")
@danieln Thanks for your response! Now we have more insight into what might be the root cause. > [@danieln](#): > > You can test the resolution manually as follows: > > ```auto > curl -H "accept: application/dns-json" "https://resolver.cloudflare-eth.com/dns-query?name=pantherprotocol.eth&type=TXT" > > ``` I will try to run this command next time and see if the ENS domain is not accessible on the Cloudflare side! > [@danieln](#): > > If you are running your own gateway node, you can configure Kubo to use the `eth.limo` DNS over HTTPS resolver: [kubo/config.md at master · ipfs/kubo · GitHub](https://github.com/ipfs/kubo/blob/master/docs/config.md#dns). Good suggestion, we will try to do this! Thanks again for your help!