_DNSLink records are TXT records that point to IPFS hashes, for pointing to changing content over time.

I’m wondering if there are any #DNS scanning services that might give some idea of how many #DNSLink records there are in the wild

Just loaded my first #p2p site published to the new version of https://distributed.press with proper #ipfs #hypercore and #dnslink support!

The DNSLink stuff is a bit iffy for hypercore, but I'll be fixing that up tomorrow.

Now stuff can be published via Distributed Press, and viewed via @agregore

What's cool is that in addition to keeping your content online, you can easily configure it to set up DNS keys for you by delegating with an NS DNS entry for the `_dnslink` subdomain on your domain.

New in #LibResilient — two #DNSLink based transport plugins:
https://resilient.is/blog/new-dnslink-based-transport-plugins/

DNSLink makes a lot of sense in LibResilient: DNS is often more reliable than web, and DNSLink offers a way to make certain information — here: where to fetch content from — available in case the main site is down without having to put that in the configuration.

This means more flexibility in case main site is down. Easier to push out updates related to alternative endpoints or current IPFS CID.

Today I am healthy and alive.😜 I was hacking #ipfs especially #dnslink for my website. And, disabled cache for one of my #GitlabCi jobs. Get faster! Hurray!