home.social

#dnsrootserver — Public Fediverse posts

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

  1. I can totally imagine the current US administration, or a future US administration, weaponizing the DNS root servers. Are there some national or international initiatives to mitigate this risk ?

    #uspol #usa #dns #DNSRootServer #intpol #internetgovernance

  2. I can totally imagine the current US administration, or a future US administration, weaponizing the DNS root servers. Are there some national or international initiatives to mitigate this risk ?

    #uspol #usa #dns #DNSRootServer #intpol #internetgovernance

  3. I can totally imagine the current US administration, or a future US administration, weaponizing the DNS root servers. Are there some national or international initiatives to mitigate this risk ?

    #uspol #usa #dns #DNSRootServer #intpol #internetgovernance

  4. I can totally imagine the current US administration, or a future US administration, weaponizing the DNS root servers. Are there some national or international initiatives to mitigate this risk ?

    #uspol #usa #dns #DNSRootServer #intpol #internetgovernance

  5. I can totally imagine the current US administration, or a future US administration, weaponizing the DNS root servers. Are there some national or international initiatives to mitigate this risk ?

    #uspol #usa #dns #DNSRootServer #intpol #internetgovernance

  6. Ever wondered why 13 is such an oddly specific number for #DNS #rootservers? Turns out that you could at most cram 13 domain names and their corresponding #IPv4 addresses in a non-truncated #UDP response. As soon as DNS truncates, the resolver falls back to #TCP. To avoid this additional performance impact and stress to the servers, the number is limited to 13.

    blog.apnic.net/2017/02/15/the-

    #Internet #criticalinfrastructure #dnsrootserver

  7. Ever wondered why 13 is such an oddly specific number for #DNS #rootservers? Turns out that you could at most cram 13 domain names and their corresponding #IPv4 addresses in a non-truncated #UDP response. As soon as DNS truncates, the resolver falls back to #TCP. To avoid this additional performance impact and stress to the servers, the number is limited to 13.

    blog.apnic.net/2017/02/15/the-

    #Internet #criticalinfrastructure #dnsrootserver

  8. Ever wondered why 13 is such an oddly specific number for #DNS #rootservers? Turns out that you could at most cram 13 domain names and their corresponding #IPv4 addresses in a non-truncated #UDP response. As soon as DNS truncates, the resolver falls back to #TCP. To avoid this additional performance impact and stress to the servers, the number is limited to 13.

    blog.apnic.net/2017/02/15/the-

    #Internet #criticalinfrastructure #dnsrootserver

  9. Ever wondered why 13 is such an oddly specific number for #DNS #rootservers? Turns out that you could at most cram 13 domain names and their corresponding #IPv4 addresses in a non-truncated #UDP response. As soon as DNS truncates, the resolver falls back to #TCP. To avoid this additional performance impact and stress to the servers, the number is limited to 13.

    blog.apnic.net/2017/02/15/the-

    #Internet #criticalinfrastructure #dnsrootserver