Why not use a regular DNS cache? If neither your ISP nor your router's cache are fast enough, then set up Unbound or systemd-resolved or dnsmasq or pdnsd.

I'm using dnsmasq but that's alone doesn't quite cache all the dns properly
because I'm still getting a "Resolving host..." message for some websites
even though I've been to those pages many many times.

So I made that bash script and problem fixed :)

How about yours? Are "Resolving host..." message still appear in your
Chrome browser while dnsmasq is up and running?

I mean Chromium browser*

As mentioned in title - not really a bug report but a way to prepopulate /etc/hosts.

If you have cases where you think Chrome is failing to do DNS resolution well and can provide some logs to help us diagnose, that would be much appreciated!