I've a #DNS related question that I'm not sure about. I currently use Hurricane Electric for my DNS even though my domain is at #MythicBeasts and they do offer a DNS service too but I'm unsure whether I should just stay with HE or move my DNS records to Mythic Beasts ?? Privacy reasons ??

Please boost for a larger reach and thank you ❤️

I've a #DNS related question that I'm not sure about. I currently use Hurricane Electric for my DNS even though my domain is at #MythicBeasts and they do offer a DNS service too but I'm unsure whether I should just stay with HE or move my DNS records to Mythic Beasts ?? Privacy reasons ??

Please boost for a larger reach and thank you ❤️

Hey — does anybody know if someone's doing research into geographic analysis of #DNS hyper-recursor (Google, Cloudflare, Quad9, etc) query patterns?

I got a goofy idea into my head this morning and when I went to do a very rough PoC, the initial findings were maybe a little more concerning (from a #privacy perspective) than I would have hoped.

I'm not an academic / trained research person, so I figured I'd see if any grown-ups had looked into this before I wasted too much time. 😉

boost_ok

Proposal to synchronize the caches of #DNS resolvers (when they are under the same organisation). "Because it is greener"

Just by sending the results of a resolution to your friends.

Implemented in Unbound at the IETf hackathon

#IETF123

Proposal to be able to delegate to . (dot) to indicate there is a zone cut without sending it (useful for split namespaces).

Zone cut to nowhere:

internal.example.com. IN NS .

#DNS#IETF123

Proposal for reserving probe.resolver.arpa as the name to use when testing a #DNS resolver. (Save resources, avoid fingerprinting, consistent results, etc)

https://mastodon.gougere.fr/@DNSresolver/114913405013969936

#IETF123

DNSOP working group: a lot of small (and somestimes not so small) changes to datatracker.ietf.org/meeting/1

First: persistent references to services you authorize (such as CAA, wallets or also what Bluesky is doing). Related but not identical to TXT-based validation with a cookie/nonce/token in it.

Many Internet protocols are already specified in EverParse (but not #DNS, alas).

#IETF123

@aeris « Les serveurs de noms de la zone parente retournent des serveurs faisant autorité (a.ns.nonamedomain.hu; b.ns.nonamedomain.hu) qui ne le sont pas par les serveurs de noms de la zone. » (Zonemaster)

#DNS

Pascal
Pascal boosted

Beta Update - Network Programming in Elixir and Erlang
by Andrea Leopardi @whatyouhide
https://pragprog.com/titles/alnpee?utm_source=m

B8.0 Release Notes:
* The book is content complete and headed to production for copy edit and layout.

(Already purchased? Check your email for a download link.)
#BEAM #erlang #elixir#TCP#UDP#DNS#HTTP

Beta Update - Network Programming in Elixir and Erlang
by Andrea Leopardi @whatyouhide
https://pragprog.com/titles/alnpee?utm_source=m

B8.0 Release Notes:
* The book is content complete and headed to production for copy edit and layout.

(Already purchased? Check your email for a download link.)
#BEAM #erlang #elixir#TCP#UDP#DNS#HTTP

Other #DNS issue: censorship transparency. "You bad user, no cookie". How to report to the user that the resource was censored?

#IETF123

And now, #DNS again, with the DNSOP working group. Several things on the agenda: https://datatracker.ietf.org/meeting/123/materials/agenda-123-dnsop-01

Including JSON in DNS error messages 😄

#IETF123

Other discussion: when a non-DELEG resolver queries an authoritative name server for a name which has only DELEG (not legacy NS), which answer? NXDOMAIN (nooooooo!)? SERVFAIL? NOTIMP?

Warning: there are interactions with DNSSEC here (you need to prove the answer).

#DNS#IETF123