Reported issue that came up on #alpine-linux: https://code.google.com/a/google.com/p/public-dns/issues/detail?id=1838 …
MX is cited there as a special case where you can't use a truncated result.
-
-
And the "SHOULD try...TCP" is conditional on "if the requester supports TCP".
-
come on, 1123 is RFC from 1989 that's been amended several times, most notably 2181.
-
I'm not going by spec but by what behavior is fundamentally necessary for decent UX.
-
Multiple round trips to get 100 extra A's you don't want or need is not decent UX.
-
The correct behavior, partial truncation, gives client a choice (TC bit) whether to ask for full rrset...
-
...or whether to use one of the first 100 A's it already got.
End of conversation
New conversation -
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.