so in your setup I'm assuming you talk to 8.8.8.8 directly?
RFC 1035 has everything a stub needs. Advanced features are for inter-DNS use, not stub-to-DNS.
-
-
If a static-linked ping from 1989 doesn't work with your dns, it's your dns that's broken, not the stub.
-
this is wrong analogy. You're asking for improved UX and refuse to use improved version of the protocol
-
The "improved" version has worse ux. 4x or worse latency.
-
again no, edns has nothing to do with latency.
-
Yes it does. 1. You have to query for support. 2. Fragmentation + packet loss = awful.
-
1. no 2. no unless you want more than path MTU, if you stick with 1280/1452 you're good.
-
1. Yes; a stub can't assume edns. There are countless isp nameservers of various brokenness.
-
2. I've seen links with MTU=576; this is likely why DNS chose 512 as limit.
End of conversation
New conversation -
-
-
it also has indivisible rrsets which you apparently want. Fortunately nothing lasts forever.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.