Maven (famous)@lemmy.world to Programmer Humor@lemmy.ml · 10 months agoSome Valentine's Lovelemmy.worldimagemessage-square32fedilinkarrow-up1361arrow-down134
arrow-up1327arrow-down1imageSome Valentine's Lovelemmy.worldMaven (famous)@lemmy.world to Programmer Humor@lemmy.ml · 10 months agomessage-square32fedilink
minus-squareEager Eagle@lemmy.worldlinkfedilinkEnglisharrow-up14arrow-down1·10 months ago9.9.9.9 has twice the latency for me. Why pick quad9 over, say, 1.1.1.2?
minus-squareFutileRecipe@lemmy.worldlinkfedilinkarrow-up1arrow-down1·10 months agoTwice the latency for DNS results? Care to give concrete examples? DNS is usually very fast. Twice as long as very fast is still pretty quick, in my opinion.
minus-squareEager Eagle@lemmy.worldlinkfedilinkEnglisharrow-up2·edit-210 months agoI’m always on VPN, so latencies add up. dig +stats @1.1.1.1 www.google.com | grep '[\d]+ msec' gives me 10-20ms using a nearby vpn server dig +stats @9.9.9.9 www.google.com | grep '[\d]+ msec' gets me 30-50 ms, and not rarely >100ms.
minus-squaresloppy_diffuserlinkfedilinkEnglisharrow-up1·9 months agoPlus DNS caching… I do DOT or DOH (forget which, setup years ago) from my router’s local DNS server without any noticeable latency.
9.9.9.9 has twice the latency for me. Why pick quad9 over, say, 1.1.1.2?
Swiss
Twice the latency for DNS results? Care to give concrete examples? DNS is usually very fast. Twice as long as very fast is still pretty quick, in my opinion.
I’m always on VPN, so latencies add up.
dig +stats @1.1.1.1 www.google.com | grep '[\d]+ msec'gives me 10-20ms using a nearby vpn server
dig +stats @9.9.9.9 www.google.com | grep '[\d]+ msec'gets me 30-50 ms, and not rarely >100ms.
Plus DNS caching… I do DOT or DOH (forget which, setup years ago) from my router’s local DNS server without any noticeable latency.