3 ms·

Anything you can "time nslookup" in or under 0.03 seconds (in "real" terms). From my desk: local one - 0.029 seconds 1.1.1.1 - 0.035 seconds 8.8.8

Anything you can "time nslookup" in or under 0.03 seconds (in "real" terms). From my desk: local one - 0.029 seconds 1.1.1.1 - 0.035 seconds 8.8.8.8 - 0.120 seconds Normally it should be, but Firefox's behavior is very sensitive to DNS response speed. Sounds not intuitive, but I think they're not using glibc's caching, or doing something by themselves.

aidenn0 3y ago
In the past, at least, firefox has done its own caching since expiring my OS dns cache was insufficient to get it to pick up a change in DNS.
- CmdrKrool 3y ago
  Good reason to avoid Firefox for development imo. Nothing is more annoying than mysterious cache interventions when you're trying to get a handle on an unrelated problem.
  - bayindirh 3y ago
    Dev tools automatically disables caching for that tab, by default. CTRL+SHIFT+R always disables cache for that reload, too.
    - aidenn0 3y ago
      I didn't know about devtools doing that; C-S R is what I use when I run into it.
      - bayindirh 3y ago
        On the Dev Tools’ network tab, there should be a checkbox about it on the top left.
    - CmdrKrool 3y ago
      In the dev tools settings there is a checkbox "Disable HTTP Cache (when toolbox is open)" which name seems to imply that this only applies to the resources that make up the page, not to DNS lookups (about:config name is devtools.cache.disabled, and it defaults to false). I investigated and found that Firefox's in-memory DNS cache can be manually cleared by clicking a button in about:networking. To be fair Chrome also has a similar cache and method for clearing it. See: https://www.makeuseof.com/chrome-edge-firefox-safari-opera-browser-clear-dns-cache/ https://www.makeuseof.com/chrome-edge-firefox-safari-opera-b...
EVa5I7bHFq9mnYK 3y ago
Tried it on a few sites, yeah, 8.8.8.8 consistently returns slower.
jraph 3y ago
Curious, where does this number comes from? (0.03 seconds)
- bayindirh 3y ago
  Nothing special. Just that if I have a DNS resolving around that timeframe, Firefox becomes noticeably faster. All of the networks I have have a DNS server around that speed now, and Firefox works visibly faster on all of them. Possibly an intersection between human perception and hardware capabilities of my systems at hand.
elishah 3y ago
> "time nslookup" Or as a slightly more thorough approach, you can use something like namebench or dnsbench: https://code.google.com/archive/p/namebench https://code.google.com/archive/p/namebench https://github.com/askmediagroup/dnsbench https://github.com/askmediagroup/dnsbench
- bayindirh 3y ago
  Yeah, while it's not as thorough as these tools, the method is at least reproducible and sane, and with ~10 or so samples, you get an interval with a nice confidence. Another through method will be hyperfine[0], yet I wanted to provide a method which requires no installation and can be done in a whim, without jumps and hoops, with the tools already at hand. [0]: https://github.com/sharkdp/hyperfine https://github.com/sharkdp/hyperfine

aidenn0 3y ago

In the past, at least, firefox has done its own caching since expiring my OS dns cache was insufficient to get it to pick up a change in DNS.

CmdrKrool 3y ago
Good reason to avoid Firefox for development imo. Nothing is more annoying than mysterious cache interventions when you're trying to get a handle on an unrelated problem.
- bayindirh 3y ago
  Dev tools automatically disables caching for that tab, by default. CTRL+SHIFT+R always disables cache for that reload, too.
  - aidenn0 3y ago
    I didn't know about devtools doing that; C-S R is what I use when I run into it.
    - bayindirh 3y ago
      On the Dev Tools’ network tab, there should be a checkbox about it on the top left.
  - CmdrKrool 3y ago
    In the dev tools settings there is a checkbox "Disable HTTP Cache (when toolbox is open)" which name seems to imply that this only applies to the resources that make up the page, not to DNS lookups (about:config name is devtools.cache.disabled, and it defaults to false). I investigated and found that Firefox's in-memory DNS cache can be manually cleared by clicking a button in about:networking. To be fair Chrome also has a similar cache and method for clearing it. See: https://www.makeuseof.com/chrome-edge-firefox-safari-opera-browser-clear-dns-cache/ https://www.makeuseof.com/chrome-edge-firefox-safari-opera-b...

EVa5I7bHFq9mnYK 3y ago

Tried it on a few sites, yeah, 8.8.8.8 consistently returns slower.

jraph 3y ago

Curious, where does this number comes from? (0.03 seconds)

bayindirh 3y ago
Nothing special. Just that if I have a DNS resolving around that timeframe, Firefox becomes noticeably faster. All of the networks I have have a DNS server around that speed now, and Firefox works visibly faster on all of them. Possibly an intersection between human perception and hardware capabilities of my systems at hand.

elishah 3y ago

> "time nslookup" Or as a slightly more thorough approach, you can use something like namebench or dnsbench: https://code.google.com/archive/p/namebench https://code.google.com/archive/p/namebench https://github.com/askmediagroup/dnsbench https://github.com/askmediagroup/dnsbench

bayindirh 3y ago
Yeah, while it's not as thorough as these tools, the method is at least reproducible and sane, and with ~10 or so samples, you get an interval with a nice confidence. Another through method will be hyperfine[0], yet I wanted to provide a method which requires no installation and can be done in a whim, without jumps and hoops, with the tools already at hand. [0]: https://github.com/sharkdp/hyperfine https://github.com/sharkdp/hyperfine