@k1ba yes, it's a way to get the primary nameserver for a zone via the API instead of DNS. Not sure if people depend on it but I wouldn't remove it either.

(Feel free to join #servfail-dev on irc.hackint.org if you have more questions, that's a bit easier for us)

~f
ns2.famfo.xyz is currently unreachable due to a provider outage ~f

#SERVFAIL
oh, and i guess we have DNS stuff too #SERVFAIL

- ~410 queries per second served on average
- most from ns1.famfo.xyz (~90) and ns1.homecloud.lol (~60).

from service updates: we're aiming to establish some better communication channels (read: a webpage with updates and an RSS feed), plus business as usual (we're slowly working on updates but our other sideprojects have been eating a lot of time lol). s00n™

~d
#SERVFAIL Q1 report:

our users have meowed in the IRC at least 92 times
see, #SERVFAIL cannot see your DMs… easy win

RE: https://critter.cafe/@det/116273539920278780
We have updated our themes a bit, hopefully making stuff slightly more legible, consistent and intuitive to use.

Please do let us know if the redesign actually achieves this goal (and if you happen to know about UI design, feel free to join us in #servfail-ui on irc.hackint.org

Bonus chart: query by IP version we get

#SERVFAIL

Stop sending us corrupt packets!1!11

#SERVFAIL

finally migrated to #servfail >:333333

finally free from cloudflare  

Heads up, we have altered the responses of our DynDNS endpoint. If your scripts depend on it, this will break them!

TLDR: positive responses are prefixed with "OK" and always have a status code of 200, negative responses are prefixed with "NOK" and have a non-200 status code.

See our docs for more information:

https://docs.servfail.network/ddns/#responses

#SERVFAIL
Dynamic DNS - SERVFAIL docs

Documentation of the simple ddns endpoint