Make of this what you will... Just now I opened up my history with Wireshark running in the background. The packet capture caught a DNS query for history.googl

Make of this what you will... Just now I opened up my history with Wireshark running in the background. The packet capture caught a DNS query for history.google.com at the same time I opened the browser history. My ISP doesn't have IPv6, so the initial connection using the AAAA record failed ~0.1 seconds later. After ~0.3 seconds it connected to the A record's IPv4 (172.253.122.102). I saw the connection to this IP address last approximately 25 seconds. Whatever is happening here, it seems like IPv4 / IPv6 connectivity may affect how users access their browser history. That history.google.com.domain is interesting. It's an alias for my activity.google.com and contains records for everything you do on Google's websites and in Google Chrome. Even if you have a different search provider in Chrome, your omnibar search query will appear there on that website. It may be syncing your browser history to Google and across other Chrome installations you've signed into.