Hacker News Reader

Comment by bluejekyll | Hacker News Reader

I don’t understand this:

  A, AAAA, TXT - set record

  A, AAAA - check key

  TXT - read value

Dynamic DNS supports all of these options directly. Why are additional records used for the key and value? IXFR could instead be used to check if a record is up-to-date rather than overloading A and AAAA in their meaning?

I’m probably missing something about how these records are meant to be used together. Is there a protocol doc available?

View on HN

The page says:

    Insert:
    · value.key.

So if you

    $ dig txt value.key.dnskv.com

you will receive an "ok" if setting key=value succeeded. Then if you

    $ dig txt key.dnskv.com

you will get the answer "value".

Read more of the page to find out what else you can do.

thanks, the docs could be more verbose. for those who don't know how does the updating work:

  dig txt u[update-secret].value.key.dnskv.com # set for first time
  dig txt u[update-secret].new-value.key.dnskv.com # use the same update secret, noone can now use this key without it until expiry

also helps to add

  dig @ns.dnskv.com. txt ...

to prevent caching or what it's called in DNS

I can't find any docs other than what's on the page but my reading suggests that the idea is that you can get/set values "in-band" using a regular lookup query to a resolver rather than the nsupdate style that you'd normally use to remotely configure zones.

I interpreted this as:

insert with any type of query to value.key.dnskv.com

check if key is set with A or AAAA query to key.dnskv.com

read value of key with TXT query to key.dnskv.com

Reply on news.ycombinator.com