Purr Specification

Personal Resource Records - Unintended DNS usage

A purr is a Personal Resource Record (prr, but purr sounds better doesn't it?)

Quick Glossary

• purr / prr: Personal Resource Record. Publishing stuff to DNS records
• rmap: RRs on a specific subdomain that help map out the layout of your purr
• rlog: An example usecase; blogging via purr. You can pronounce it as "ruh-log"

The basic idea is this: Using DNS TXT records, publish text, info, blogposts or any other data you want.

The specification is simple:

• Separate categories of content by creating new subdomains.
• always create a resource map on a subdomain called rmap.<your-domain>.<tld>
• in the rmap, list the other subdomains the user can query for different categories. always start the string for these with a #
• Have fun and get creative. This is really a very basic specification.

Advice: except perhaps some very rare cases, DNS RRs will never be returned in a specific order. Therefore do not create your TXT records on the assumptiont that they will maintain sequence (e.g. rlog posts will not be in any chronological order)

You can see a demo by opening up a terminal and doing dig TXT c0co.channel

contact: cc[@]c0co.ch

purr: # dig TXT c0co.channel