2024-11-25 bortzmeyer ┃ 1#️ 2👤 1💬 ┃ RE: ?
@kamyk @quad9dns Funny that people on the fediverse boast they use a decentralized social network to avoid big capitalist social networks but then use public #DNS resolvers managed by big US […]
2024-11-21 bortzmeyer ┃ 1#️ 2👤 1💬 ┃ RE: ?
@shaft @xalofar Et on peut utiliser n'importe quel client DNS comme dig. C'est du #DNS normal.
2024-11-21 bortzmeyer ┃ 1🔗 1#️ 1👤 1💬
Time to start a contest with @jpmens
#DNS
2024-11-18 bortzmeyer ┃ 1🔗 1#️ 2💬
Si vous voyez apparaitre un @bortzmeyer.org sur le truc bleu, c'est moi :-) domainincite.com/30549-twitter…
#DNS
2024-11-18 bortzmeyer ┃ 1🔗 1#️ 1👤 1💬
"The #DNS Server That Lagged Behind"
Anycast, monitoring and debugging (with RIPE Atlas probes but not only).
[…]
2024-11-15 bortzmeyer ┃ 1🔗 3#️ 4💬
En France, on n'aime pas les hamsters : framagit.org/-/snippets/7403
#rongeurophobie #DNS #censure
2024-11-14 bortzmeyer ┃ 1🔗 2#️ 3💬
Je découvre que l'excellent service de publication de noms de domaines suspects red.flag.domains/ fournit aussi des fichiers de filtrage pour Pi-Hole.
#DNS #hameçonnage
2024-11-11 bortzmeyer ┃ 2#️ ┃ RE: bortzmeyer
Une question pour les géographes : les instances anycast du serveur #DNS d'#Afrinic portent des identificateurs qui ne révèlent pas clairement leur position. Si s04-ns2.jnb est très […]
2024-11-11 bortzmeyer ┃ 1🔗 2#️ 1💬
La semaine dernière, 26 #TLD africains avaient des problèmes #DNS. Pourquoi ? Parce qu'une machine quelque part ne se mettait plus à jour et servait des données erronées. […]
2024-11-11 bortzmeyer ┃ 1🔗 3#️
IETF 121 hackathon: greasing DNS answers
On November 2 and 3 was the #IETF #hackathon in Dublin. I worked on the greasing of #DNS answers from an authoritative name server. What is greasing? […]
2024-11-08 bortzmeyer ┃ 1🔗 2#️
An Internet-Draft which talks a lot about Bluesky (boasting that it allows you to have your own domain name) and not mentioning the fediverse :-( datatracker.ietf.org/doc/draft…
#DNS #IETF121
2024-11-07 bortzmeyer ┃ 4#️ 1👤 ┃ RE: bortzmeyer
Proposal to add hard numerical limits to the #DNS parameters, in order to limit DoS attacks like #KeyTrap, Infinite or #Tsuname
For instance, max. number of NS records : 13, max. number of […]
2024-11-07 bortzmeyer ┃ 1🔗 2#️ 1💬 ┃ RE: bortzmeyer
Now, DNSOP, "new work for consideration" session, we want to add funny things to the #DNS
datatracker.ietf.org/meeting/1…
[…]
2024-11-05 bortzmeyer ┃ 1🔗 2#️ 1💬 ┃ RE: bortzmeyer
ADD working group (stuff about #DNS resolvers). Nothing too important but there is a draft of mine. datatracker.ietf.org/meeting/1…
#IETF121
2024-11-05 bortzmeyer ┃ 1🔗 2#️ 1💬
Good morning, Dublin! Fourth day of #IETF121. ietf.org/meeting/121/
For me, today, digital emblems (marks on networks or domains to show that you should not attack them, like the Red Cross n […]
2024-11-04 bortzmeyer ┃ 2#️ ┃ RE: bortzmeyer
#DNS transports: "DoU, DoTCP, DoT, DoH, DoQ, DoHQ, DoAvianCarrier…"
#IETF121
2024-11-04 bortzmeyer ┃ 2🔗 2#️ 1💬 ┃ RE: bortzmeyer
First, domain control validation with the #DNS. Proving that you control something.com.
You know, all these TXT records at the apex, too large for Mastodon : botsin.space/@DNSresolver/1134… […]
2024-11-04 bortzmeyer ┃ edited ┃ 1🔗 2#️ 1💬 ┃ RE: bortzmeyer
Now, DNSOP, to save the #DNS (and the planet, and the galaxy) datatracker.ietf.org/meeting/1…
#IETF121
2024-11-04 bortzmeyer ┃ edited ┃ 2#️ 1💬 ┃ RE: bortzmeyer
The two solutions fit the requirments and have similar properties but:
1) will require changes to #DNS resolvers and auth. servers
2) will require changes to resolvers only, will introduce a […]
2024-11-04 bortzmeyer ┃ edited ┃ 1🔗 2#️ 1💬 ┃ RE: bortzmeyer
Let's start with the new DELEG working group: the goal is to change completely the #DNS delegation, thus requiring to change auth. servers, resolvers, debugging tools, EPP, RDAP, slides for […]
2024-11-04 bortzmeyer ┃ 1🔗 2#️ 1💬
Good morning, Dublin! Third day of the #IETF121 (and first of the working groups meetings).
Today, my agenda is full: DELEG (completely changing the DNS delegation), Regext (EPP and RDAP), […]
2024-11-03 bortzmeyer ┃ 2#️ 1💬 ┃ RE: bortzmeyer
The good thing about DELEG is that we will probably still work on it at the IETF hackathon in 2030 or 2040.
#DNS #IETF121
2024-11-03 bortzmeyer ┃ 2#️ 1💬 ┃ RE: bortzmeyer
#DNS various projects: CHAIN requests (sending all DNSSEC keys in the reply, RFC 7901), greasing the DNS, new ways to rollover keys, multi-signer again, and of course beginning of the work on […]
2024-11-03 bortzmeyer ┃ 3#️ 1💬 ┃ RE: bortzmeyer
#DNS encoded in #CBOR (for IoT). Two implementations (including one in RIOT.)
(Not related to C-DNS.]
[…]
Setting up an experimental #DNS server at #IETF121 hackathon allows you to see bots crawling the IPv4 address space looking for DNS reflectors. I discovered this way several domains with high […]
2024-11-03 bortzmeyer ┃ edited ┃ 1🔗 2#️
Good morning, Dublin! Second day of #IETF121, we continue the hackathon ietf.org/meeting/hackathons/12…
(My work: greasing the #DNS)
Il y a deux tchèques qui parlent de #DNS à côté de moi et je n'y comprends rien.
#IETF121
2024-10-29 bortzmeyer ┃ 2🔗 1#️
Funny #DNS TXT records, a thread on Twitter: x.com/repa_martin/status/18506…
Example: botsin.space/@DNSresolver/1133…
2024-10-28 bortzmeyer ┃ edited ┃ 1#️ 1💬
J'utilise dans mes cours #DNS un domaine réel qui a beaucoup d'erreurs. Après le dernier cours, je me suis dit que j'étais vache et que je devais plutôt envoyer au gérant du domaine un rapport […]
────
────