home.social

#svcb — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #svcb, aggregated by home.social.

  1. je découvre le truc et je vois pas l'info, mais est-ce qu'il est possible d'utiliser #svcb pour par exemple permettre à un client openvpn de se connecter automatiquement à un lien de secours si le lien principal ne répond pas ?

    Ca pourrait marcher ou je capte pas le truc ?

  2. je découvre le truc et je vois pas l'info, mais est-ce qu'il est possible d'utiliser #svcb pour par exemple permettre à un client openvpn de se connecter automatiquement à un lien de secours si le lien principal ne répond pas ?

    Ca pourrait marcher ou je capte pas le truc ?

  3. je découvre le truc et je vois pas l'info, mais est-ce qu'il est possible d'utiliser #svcb pour par exemple permettre à un client openvpn de se connecter automatiquement à un lien de secours si le lien principal ne répond pas ?

    Ca pourrait marcher ou je capte pas le truc ?

  4. je découvre le truc et je vois pas l'info, mais est-ce qu'il est possible d'utiliser #svcb pour par exemple permettre à un client openvpn de se connecter automatiquement à un lien de secours si le lien principal ne répond pas ?

    Ca pourrait marcher ou je capte pas le truc ?

  5. je découvre le truc et je vois pas l'info, mais est-ce qu'il est possible d'utiliser #svcb pour par exemple permettre à un client openvpn de se connecter automatiquement à un lien de secours si le lien principal ne répond pas ?

    Ca pourrait marcher ou je capte pas le truc ?

  6. @cks @lanodan

    Missing from @drscriptt 's list are AAAA, HTTPS, and SVCB records.

    AAAA has plenty of obvious choices.

    You'll know the . convention for SRV, SVCB, and MX resource record sets, of course.

    I shall just drop in my personal experience from earlier this year that an accidentally supplied HTTPS resource record can *definitely* break WWW traffic; because browsers in practice do not obey RFC9460 §2.4.2.

    #djbdns
    #DomainNameSystem
    #SplitHorizon
    #ReservedSuperDomains #DNS #HTTPS #SVCB

  7. @cks @lanodan

    Missing from @drscriptt 's list are AAAA, HTTPS, and SVCB records.

    AAAA has plenty of obvious choices.

    You'll know the . convention for SRV, SVCB, and MX resource record sets, of course.

    I shall just drop in my personal experience from earlier this year that an accidentally supplied HTTPS resource record can *definitely* break WWW traffic; because browsers in practice do not obey RFC9460 §2.4.2.

    #djbdns
    #DomainNameSystem
    #SplitHorizon
    #ReservedSuperDomains #DNS #HTTPS #SVCB

  8. @cks @lanodan

    Missing from @drscriptt 's list are AAAA, HTTPS, and SVCB records.

    AAAA has plenty of obvious choices.

    You'll know the . convention for SRV, SVCB, and MX resource record sets, of course.

    I shall just drop in my personal experience from earlier this year that an accidentally supplied HTTPS resource record can *definitely* break WWW traffic; because browsers in practice do not obey RFC9460 §2.4.2.

    #djbdns
    #DomainNameSystem
    #SplitHorizon
    #ReservedSuperDomains #DNS #HTTPS #SVCB

  9. @cks @lanodan

    Missing from @drscriptt 's list are AAAA, HTTPS, and SVCB records.

    AAAA has plenty of obvious choices.

    You'll know the . convention for SRV, SVCB, and MX resource record sets, of course.

    I shall just drop in my personal experience from earlier this year that an accidentally supplied HTTPS resource record can *definitely* break WWW traffic; because browsers in practice do not obey RFC9460 §2.4.2.

    #djbdns
    #DomainNameSystem
    #SplitHorizon
    #ReservedSuperDomains #DNS #HTTPS #SVCB

  10. 🚨 BREAKING: #RFC9460 claims to revolutionize the #DNS landscape with #SVCB and #HTTPS records, but spoiler alert—it's just another jargon-filled proposal destined to collect digital dust. 🌐📜 Meanwhile, DNS admins everywhere are thrilled to have more acronyms to ignore. 🙄✨
    datatracker.ietf.org/doc/html/ #DigitalDust #DNSAdmins #HackerNews #ngated

  11. 🚨 BREAKING: #RFC9460 claims to revolutionize the #DNS landscape with #SVCB and #HTTPS records, but spoiler alert—it's just another jargon-filled proposal destined to collect digital dust. 🌐📜 Meanwhile, DNS admins everywhere are thrilled to have more acronyms to ignore. 🙄✨
    datatracker.ietf.org/doc/html/ #DigitalDust #DNSAdmins #HackerNews #ngated

  12. 🚨 BREAKING: #RFC9460 claims to revolutionize the #DNS landscape with #SVCB and #HTTPS records, but spoiler alert—it's just another jargon-filled proposal destined to collect digital dust. 🌐📜 Meanwhile, DNS admins everywhere are thrilled to have more acronyms to ignore. 🙄✨
    datatracker.ietf.org/doc/html/ #DigitalDust #DNSAdmins #HackerNews #ngated

  13. 🚨 BREAKING: #RFC9460 claims to revolutionize the #DNS landscape with #SVCB and #HTTPS records, but spoiler alert—it's just another jargon-filled proposal destined to collect digital dust. 🌐📜 Meanwhile, DNS admins everywhere are thrilled to have more acronyms to ignore. 🙄✨
    datatracker.ietf.org/doc/html/ #DigitalDust #DNSAdmins #HackerNews #ngated

  14. @ermo

    There are a much smaller number of people doing SVCB lookups, too. But, interestingly, they are doing them wrongly.

    And with a direct correlation to some other abuses.

    Which does make me think that, in an ironic twist, it is the bad actors running robot vulnerability probes and scrapers that are the early adopters of SVCB, here.

    #djbwares #DomainNameSystem #svcb

  15. @ermo

    There are a much smaller number of people doing SVCB lookups, too. But, interestingly, they are doing them wrongly.

    And with a direct correlation to some other abuses.

    Which does make me think that, in an ironic twist, it is the bad actors running robot vulnerability probes and scrapers that are the early adopters of SVCB, here.

    #djbwares #DomainNameSystem #svcb

  16. @ermo

    There are a much smaller number of people doing SVCB lookups, too. But, interestingly, they are doing them wrongly.

    And with a direct correlation to some other abuses.

    Which does make me think that, in an ironic twist, it is the bad actors running robot vulnerability probes and scrapers that are the early adopters of SVCB, here.

    #djbwares #DomainNameSystem #svcb

  17. Today I discovered the RFC 9460 and therefore the SVCB and HTTPS resource records. Very interesting and useful innovation :)

    https://www.rfc-editor.org/rfc/rfc9460

    #RFC9460 #RFC #DNS #SVCB #HTTPS

  18. Today I discovered the RFC 9460 and therefore the SVCB and HTTPS resource records. Very interesting and useful innovation :)

    https://www.rfc-editor.org/rfc/rfc9460

    #RFC9460 #RFC #DNS #SVCB #HTTPS

  19. Today I discovered the RFC 9460 and therefore the SVCB and HTTPS resource records. Very interesting and useful innovation :)

    https://www.rfc-editor.org/rfc/rfc9460

    #RFC9460 #RFC #DNS #SVCB #HTTPS

  20. We now publish DNS HTTPS IP hint records for all #OpenStreetMap web services per #RFC9460 Why? Small incremental improvement to performance and privacy. Our DNS handles over 2,000 requests per second. DNS HTTPS query is our 2nd most common query. #DNScontrol #SVCB 🚀 🤓

  21. We now publish DNS HTTPS IP hint records for all #OpenStreetMap web services per #RFC9460 Why? Small incremental improvement to performance and privacy. Our DNS handles over 2,000 requests per second. DNS HTTPS query is our 2nd most common query. #DNScontrol #SVCB 🚀 🤓

  22. We now publish DNS HTTPS IP hint records for all #OpenStreetMap web services per #RFC9460 Why? Small incremental improvement to performance and privacy. Our DNS handles over 2,000 requests per second. DNS HTTPS query is our 2nd most common query. #DNScontrol #SVCB 🚀 🤓

  23. We now publish DNS HTTPS IP hint records for all #OpenStreetMap web services per #RFC9460 Why? Small incremental improvement to performance and privacy. Our DNS handles over 2,000 requests per second. DNS HTTPS query is our 2nd most common query. #DNScontrol #SVCB 🚀 🤓

  24. We now publish DNS HTTPS IP hint records for all #OpenStreetMap web services per #RFC9460 Why? Small incremental improvement to performance and privacy. Our DNS handles over 2,000 requests per second. DNS HTTPS query is our 2nd most common query. #DNScontrol #SVCB 🚀 🤓

  25. "ohttp" is now officialy the 8th wonder of the "Service Parameter Keys (SvcParamKeys)" registry :)

    (And is the easiest to process when decoding a #SVCB RR :) )

    #RFC 9540: Discovery of Oblivious Services via Service Binding Records
    rfc-editor.org/info/rfc9540

  26. "ohttp" is now officialy the 8th wonder of the "Service Parameter Keys (SvcParamKeys)" registry :)

    (And is the easiest to process when decoding a #SVCB RR :) )

    #RFC 9540: Discovery of Oblivious Services via Service Binding Records
    rfc-editor.org/info/rfc9540

  27. "ohttp" is now officialy the 8th wonder of the "Service Parameter Keys (SvcParamKeys)" registry :)

    (And is the easiest to process when decoding a #SVCB RR :) )

    #RFC 9540: Discovery of Oblivious Services via Service Binding Records
    rfc-editor.org/info/rfc9540

  28. "ohttp" is now officialy the 8th wonder of the "Service Parameter Keys (SvcParamKeys)" registry :)

    (And is the easiest to process when decoding a #SVCB RR :) )

    #RFC 9540: Discovery of Oblivious Services via Service Binding Records
    rfc-editor.org/info/rfc9540

  29. "ohttp" is now officialy the 8th wonder of the "Service Parameter Keys (SvcParamKeys)" registry :)

    (And is the easiest to process when decoding a #SVCB RR :) )

    #RFC 9540: Discovery of Oblivious Services via Service Binding Records
    rfc-editor.org/info/rfc9540

  30. There is a great summary of the state of HTTPS RRs (#SVCB style records) at netmeister.org/blog/https-rrs.
    Thanks @jschauma for writing this – it also explains in its footnotes why Chromium so far fails my svcbtest.amsuess.com/ test site – it doesn't allow setting a different target name.

  31. There is a great summary of the state of HTTPS RRs (#SVCB style records) at netmeister.org/blog/https-rrs.
    Thanks @jschauma for writing this – it also explains in its footnotes why Chromium so far fails my svcbtest.amsuess.com/ test site – it doesn't allow setting a different target name.

  32. There is a great summary of the state of HTTPS RRs (#SVCB style records) at netmeister.org/blog/https-rrs.
    Thanks @jschauma for writing this – it also explains in its footnotes why Chromium so far fails my svcbtest.amsuess.com/ test site – it doesn't allow setting a different target name.

  33. There is a great summary of the state of HTTPS RRs (#SVCB style records) at netmeister.org/blog/https-rrs.
    Thanks @jschauma for writing this – it also explains in its footnotes why Chromium so far fails my svcbtest.amsuess.com/ test site – it doesn't allow setting a different target name.

  34. There is a great summary of the state of HTTPS RRs (#SVCB style records) at netmeister.org/blog/https-rrs.
    Thanks @jschauma for writing this – it also explains in its footnotes why Chromium so far fails my svcbtest.amsuess.com/ test site – it doesn't allow setting a different target name.

  35. Oh, and lastly, this whole Mastodon thread as a much more convenient blog post 😜:

    netmeister.org/blog/https-rrs.

    #dns #svcb #https #rfc9460 ✌️

  36. Oh, and lastly, this whole Mastodon thread as a much more convenient blog post 😜:

    netmeister.org/blog/https-rrs.

    ✌️

  37. Oh, and lastly, this whole Mastodon thread as a much more convenient blog post 😜:

    netmeister.org/blog/https-rrs.

    #dns #svcb #https #rfc9460 ✌️

  38. Oh, and lastly, this whole Mastodon thread as a much more convenient blog post 😜:

    netmeister.org/blog/https-rrs.

    #dns #svcb #https #rfc9460 ✌️

  39. Oh, and lastly, this whole Mastodon thread as a much more convenient blog post 😜:

    netmeister.org/blog/https-rrs.

    #dns #svcb #https #rfc9460 ✌️

  40. @jschauma They’re pretty great. #HTTPS records are self-explanatory, but do you know of any services using #SVCB yet?