If you can see this, I moved hosting for terse.telent.net from Bytemark to Mythic Beasts. This is the first of several services that need migrating from my old VM to my new one.

(The zeroth was DNS: now instead of using Bytemark's content dns I am running an actual DNS server with actual zone files, and I cannot tell you how much more pleasant it is for setting up AAAA records than futzing with tinydns format files was)

self reply
in reply to Daniel Barlow
in reply to Thibaut
in reply to Daniel Barlow
in reply to Thibaut

I'm glad it works for you, obviously. On the server I was using (#ipv6-addresses">https://docs.bytemark.co.uk/article/tinydns-format/#ipv6-addresses) it didn't work for me. I don't know what patches that server may or may not have had: it does seem as though tinydns-with-ipv6 is a diverged program

Perhaps more relevantly, I tangle with DNS about three times a year on average, more often to add a "weird" record type than a standard host or MX, and on the whole I would rather be able to update my zones in the standard format than have to look up on the internet every time how to translate from the standard name for the record type into whatever sigil tinydns has allotted to it. If I were a professional hostmaster maybe I'd have a different view on this.

in reply to Daniel Barlow

@dan Yes I got it. My point was that as soon as you're self-hosted, pick the server you want with the patches you want, so no more \xxx stuff.

I agree on the benefits of using the de factor standard configuration, but zones file are so weird that I prefer to stick to tinydns.

I also like its enforcement of some "good practices" (e.g., several DNS entries for 1 configuration line). I think it makes easier to anyone to manage its DNS without really learning all the DNS' implicit knowledge.

self reply