home.social

#resolvers — Public Fediverse posts

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

  1. Exploring #DNS4EU a little further and throwing myself back to research I was involved in a while back (arxiv.org/abs/2403.05638), surprisingly shows that the #European #resolver shows no problems resolving the sanctioned entities of #RussiaToday and #Sputniknews.

    An oversight? I would be less surprised if the unfiltered #resolvers resolve the domain names, but even the protective ones resolve to the correct domain names, revealing that #DNSblocking is not applied on #EU cyber-resiliency flagship project.

    #DNS #Sanctions #RussiansSanctions #EuropeanAlternatives #Whalebone

  2. Exploring #DNS4EU a little further and throwing myself back to research I was involved in a while back (arxiv.org/abs/2403.05638), surprisingly shows that the #European #resolver shows no problems resolving the sanctioned entities of #RussiaToday and #Sputniknews.

    An oversight? I would be less surprised if the unfiltered #resolvers resolve the domain names, but even the protective ones resolve to the correct domain names, revealing that #DNSblocking is not applied on #EU cyber-resiliency flagship project.

    #DNS #Sanctions #RussiansSanctions #EuropeanAlternatives #Whalebone

  3. Exploring #DNS4EU a little further and throwing myself back to research I was involved in a while back (arxiv.org/abs/2403.05638), surprisingly shows that the #European #resolver shows no problems resolving the sanctioned entities of #RussiaToday and #Sputniknews.

    An oversight? I would be less surprised if the unfiltered #resolvers resolve the domain names, but even the protective ones resolve to the correct domain names, revealing that #DNSblocking is not applied on #EU cyber-resiliency flagship project.

    #DNS #Sanctions #RussiansSanctions #EuropeanAlternatives #Whalebone

  4. Exploring #DNS4EU a little further and throwing myself back to research I was involved in a while back (arxiv.org/abs/2403.05638), surprisingly shows that the #European #resolver shows no problems resolving the sanctioned entities of #RussiaToday and #Sputniknews.

    An oversight? I would be less surprised if the unfiltered #resolvers resolve the domain names, but even the protective ones resolve to the correct domain names, revealing that #DNSblocking is not applied on #EU cyber-resiliency flagship project.

    #DNS #Sanctions #RussiansSanctions #EuropeanAlternatives #Whalebone

  5. Exploring #DNS4EU a little further and throwing myself back to research I was involved in a while back (arxiv.org/abs/2403.05638), surprisingly shows that the #European #resolver shows no problems resolving the sanctioned entities of #RussiaToday and #Sputniknews.

    An oversight? I would be less surprised if the unfiltered #resolvers resolve the domain names, but even the protective ones resolve to the correct domain names, revealing that #DNSblocking is not applied on #EU cyber-resiliency flagship project.

    #DNS #Sanctions #RussiansSanctions #EuropeanAlternatives #Whalebone

  6. @tychi
    (2/4)… It can be switched off so #DNS is handled at the OS-level. As such, we are calling for a #trustless #DoH, which involves using lists of independent #resolvers (there's a list at the github/curl page). A few arbitrary resolvers would be chosen for each DNS request, with the returned values cross-checked. If there's a discrepancy a new request is made with a several resolvers. Again this would ideally be done at OS level. The beauty of DoH over #DoT…(2/4)