4 ms·
It would be hard to be worse. If I turn on too much of IPV6 on OSX DNS takes forever (yes I did check the IPV6 config).
by jmount 11y ago
It would be hard to be worse. If I turn on too much of IPV6 on OSX DNS takes forever (yes I did check the IPV6 config).
- breckinloggins 11y agoCan you file a radar for that with the specific things that are causing the slowdown? Radars are always appreciated.
- the_mitsuhiko 11y agoSlow DNS with some configs that involve IPv6 is a known issue on OSX :(
- jsmthrowaway 11y agoI finally pulled IPv6 resolvers out of my config for this very reason. I was getting 4+ second lookups against both Comcast and Google v6 resolvers even though direct v6 sockets worked instantly; made worse because HSTS apparently makes Chrome put "establishing secure connection" in the status bar while resolving (maybe?), so I ended up down a rabbit hole of identifying reasons for phantom TLS stalls. Finally cut down to just v4 resolvers and it's a brand new computer. Glad to know it's not just me.
- jmount 11y agoThat is pretty much what I saw. I was somewhat worried if it was the AT&T modem config or OSX, but nothing I tried fixed it (including explicitly setting DNS sources and so on).
- jmount 11y agoSure, pay me my consulting rate to run it down and fill out the forms.