derat / bind-to-tinydns Goto Github PK

I had to migrate 3000 lines of broken, mysterious BIND data in an emergency on a compromised DNS server. I did so with this utility, 10 lines of shell code and some file copying. I would give you all my bitcoins if I could. U Rule.

I'm no expert on tinydns, but the SRV records generated by bind-to-tinydns are possibly invalid. At least, they don't work with my provider's tinydns, and browsing around the web, it seems that the consensus is that SRV records should look different to how bind-to-tinydns generates them.

Currently bind-to-tinydns generates them looking like this: (a.example.com has an SRV record with priority 5 pointing to b.example.com:10):
:a.example.com:33:\000\005\000\000\000\012\016b.example.com:3600

whereas other SRV record generators for tinydns (e.g. http://anders.com/projects/sysadmin/djbdnsRecordBuilder/#SRV) generate something like this, which seems to work:
:a.example.com:33:\000\005\000\000\000\012\001b\007example\003com\000:3600

Note how the second example has the dots in the destination encoded.