treysis

You shouldn't be using `localhost` but `127.0.0.1` instead. Reason is that name resolution for localhost varies a lot between different systems and implementations of their network stacks.

@krpeacock Yes, that's why it was mentioned as a possibly breaking change and not introduced in 16, but in the short-term release 17, and also not backported to 16. @davidmeirlevy...

> Looks like Node v17+ changed to way `localhost` is being looked-up Yes, partly. It just doesn't reorder the DNS results anymore. That's what we said all the time. The...

Detecting the presence of and the prefix in use by DNS64/NAT64 should be done by querying `ipv4only.arpa`. With DNS64/NAT64 in place the AAAA lookup should yield `::192.0.0.170` and `::192.0.0.171`, as...

I believe it should be mentioned in the headline or very mich in the beginning. I mean I personally know about the staged rollout (though I only learned that 2...

> but in fact only somebody with access to the [Google Play Console](https://play.google.com/console/about/) for the CWA account can say for sure. You can just open PlayStore in an incognito window....

> Another fact that should be taken into account: the vast majority of devices running Android 5.0 do not support the necessary Bluetooth 4.0 functions. I wouldn't be so sure...

@MikeMcC399 From what I understood, Android 5 is incompatible due to a cryptographic library. Only way would be to update Android 5, which would have to be pushed by the...

> ``` > Does your NAT64 actually use the 64:ff9b::/96 prefix? I could tag that as IPv4 > trivially, but allowing arbitrary prefixes would require a configuration page, > and...

How about "(4)" (4 in brackets)? Or a green 4, or a red 6?