ok, now we've established that spec doesn't support it and servers don't do it, you argument on UX.
-
-
Replying to @vavrusam @RichFelker and
which is fair. It's be desirable in some cases. It's not in some other - when you need to validate.
1 reply 0 retweets 0 likes -
Stub resolvers do not validate. They trust a validating resolver on localhost.
2 replies 0 retweets 0 likes -
no stubs don't validate, but forwarder that would receive something from your 8.8.8.8 would have to.
1 reply 0 retweets 0 likes -
Right. The forwarder that does validation needs ability to do edns or tcp.
2 replies 0 retweets 0 likes -
so in your setup I'm assuming you talk to 8.8.8.8 directly?
1 reply 0 retweets 0 likes -
It's not my setup but a user who encountered failed lookups in musl-based containers using 8.8.8.8.
1 reply 0 retweets 0 likes -
okay, and something is preventing the stub to use edns?
1 reply 0 retweets 0 likes -
Our stub resolver intentionally doesn't do edns or tcp, for several reasons.
2 replies 0 retweets 0 likes -
Replying to @RichFelker @vavrusam and
Low latency, statelessness, ability to use same query packet concurrently w/multiple servers, etc.
2 replies 0 retweets 0 likes
Also bounding the size of the response.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.