@phils@chaos.social

· 5mo ago

Replying to

@namedbird@noc.social @nygren@hachyderm.io In practice, IPv6-only resolvers are still rare. I only encountered this due to building and operating https://webres6.dev.sap/ – an IPv6-only website/app tester.

webres6.dev.sap

IPv6 Web Resource Checker

Test whether a web site / web app is IPv6-only ready. This tool uses Selenium to load a web page and analyzes whether all resources are reachable via IPv6 by testing HTTP endpoints as well as DNS chain.

3

0

Philipp S. Tiesel @phils@chaos.social

· 5mo ago

Replying to

@kasperd@westergaard.social I don’t care whether new applications are using IPv4-mapped addresses internally, towards the local network abstraction or in persistent storage. I violently fight any attempts to put them in DNS or packets sent to the wire.

2

0

Philipp S. Tiesel @phils@chaos.social

· 5mo ago

Replying to

@Oskar456@mastodon.social @nygren@hachyderm.io True. Feel invited to also give feedback on the DNSOP list alongside with a comment whether you see the need for a draft updating RFC3901bis.

1

0

Philipp S. Tiesel @phils@chaos.social

· 5mo ago

Replying to

@namedbird@noc.social @nygren@hachyderm.io I would not call it worse but much harder to debug. In a non-trivial case with CDNs and dynamic sets of DNS servers, you get a random looking set of DNS servers of which a random fraction has AAAA records. Depending on which you pick and how many failures you tolerate, this gives you a good chance of resolve failures. Checking 10sec later with another tool behaves totally different. Checking from another vantage point behaves totally different.

1

0