4 ms·
well to be fair sometimes my firefox makes really really strange things. sometimes our internal sites won't work, because firefox resolves a IPv6 address (that
by merb 8y ago
well to be fair sometimes my firefox makes really really strange things.
sometimes our internal sites won't work, because firefox resolves a IPv6 address (that is also in our network but for another domain.) when the thing has no IPv6 address.
i.e. git.example.com has the IPv6 and sometimes sentry.example.com resolves the ipv6 of git besides not having any IPv6 AAAA entry at all. I could not find out why that is happing, since it's only happening in FF.
besides that, I also think the developer tools got better, but are still not on par with Google Chrome.
(At the moment I primarly use Firefox, besides when the bug occurs than I open these services in Safari or Chrome)
- stult 8y agoIt's actually turned into a benefit for me that the developer tools suck. I also use FF for browsing and then Chrome for debugging. Which is nice when a coworker is watching me debug over my shoulder because autocomplete never reveals the incredibly basic shit I google on a day to day basis.
- adminu 8y agoTurns out firefox uses DNS over HTTPS to resolve DNS names (if enabled), maybe you want to turn that of and check if it changes anything. https://wiki.mozilla.org/Trusted_Recursive_Resolver https://wiki.mozilla.org/Trusted_Recursive_Resolver