dnsaddr code?

[richardschneider]

The code for dnsaddr is not consistent.

• go uses code 12345
• js uses code 53
• protocols.csv does not mention dnsaddr but has a dns at code 53.

Can someone please clarify! cc: @diasdavid @whyrusleeping

[whyrusleeping]

Youre gonna have to ask @lgierth on that one. I don't know

[daviddias]

AFAIU, @lgierth renamed dns to dnsaddr, which was 53 from early days -- https://github.com/multiformats/multiaddr/blob/master/protocols.csv#L7 --. @lgierth Any reason why you didn't update the multiaddr spec and protocol table https://github.com/multiformats/multiaddr ?

12345 looks like a "typed out random number" :)

[richardschneider]

@lgierth any comment?

[ghost]

Sorry - this was a really silly oversight from early development on this :/ Let's go with js's 53.

[richardschneider]

Why dnsaddr and not just dns?

[ghost]

Actually, let's keep 53 reserved for any future /dns protocol. I've filed multiformats/multiaddr#61, #8, and multiformats/js-multiaddr#59, and @ianopolous did multiformats/java-multiaddr@3a6d6548.

@richardschneider if that's cool with you do you wanna update net-ipfs-core too? (you referenced a commit up there)

Why dnsaddr and not just dns?

dnsaddr is the multiaddr-equivalent of dnslink -- we put multiaddrs into a DNS record, and /dnsaddr lets us resolve through them. This is used e.g. in go-ipfs's default bootstrap config. /dns on the other hand should be reserved for a "broader" dns address protocol, should there ever be the need for one in the future.

[ghost]

I think this inconsistency is resolved once:

• Add /dnsaddr multiaddr#61
• Use consistent /dnsaddr code #8
• fix: use consistent /dnsaddr code js-multiaddr#59
• java-multiaddr
• net-ipfs-core

[richardschneider]

@lgierth I changed the code in net-ipfs-core, you can now tick it!

[richardschneider]

we put multiaddrs into a DNS record, and /dnsaddr lets us resolve through them.

I think I'm resolving dnsaddr incorrectly, see peer talk. Basically I'm accepting any A or AAAA resource record from DNS.

Could you detail or point me to a spec on how to resolve dnsaddr? Is this some magick/hackery with TXT records?

[ghost]

Thanks @diasdavid -- all the impls can slowly roll this out with their next releases then.

@richardschneider There's unfortunately no proper spec, only the examples in the readme of this repo.