CTRL+SHIFT+R always disables cache for that reload, too.
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-b...
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.
Or as a slightly more thorough approach, you can use something like namebench or dnsbench:
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.
From my desk:
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.