home.social

#webres6 — Public Fediverse posts

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

fetched live
  1. goetz @[email protected] ·

    @phils

    @gnome @fastlydevs @devs

    No fully.

    #Fastly #webres6

    #fastly #webres6
  2. Philipp S. Tiesel @[email protected] ·

    @goetz @gnome @fastlydevs @devs #Fastly seems to have fixed their glue records. Testing and having good tools matters - you can only fix what you are aware of. Time to build #webres6 seems to be well invested.

    #fastly #webres6
  3. goetz @[email protected] ·

    @kasperd @phils @devs @gnome @fastlydevs

    zonemaster is a sufficient tool for this to complement #webres6

    #webres6
  4. goetz @[email protected] ·

    @phils
    Yes totally agree and appreciate #webres6

    For nameservers and resolvers we now have #RFC10001 by @tfiebig and co authors.
    Which should work without glue records.

    But I assume we all look towards the day where #RFC10001bis is ready and one can drop #LegacyIP support.

    @jtk

    #webres6 #rfc10001 #rfc10001bis #legacyip
  5. goetz @[email protected] ·

    @jtk
    Thank you.
    I was trying to point out why
    the #webres6 testing does not pick them up due to #IPv6-only-strict preset of the testing resolver.
    As confirmed by Philipp.

    To add, one needs a #legacyip resolver for #fastly until this is fixed.
    Tooling like #webres6 helps finding those issues.

    #webres6 #ipv6 #legacyip #fastly
  6. goetz @[email protected] ·

    #Fastly already updated their nameservers to have AAAA records and are reachable via #IPv6 #RFC10001 🚀
    Unfortunately they forgot to add glue records thus websites like @gnome or @fastlydevs @devs are still reported as not #IPv6ready with #webres6

    @phils do I miss something?

    webres6.dev.sap/#report:6a8dd6

    #fastly #ipv6 #rfc10001 #ipv6ready #webres6