Hacker News new | ask | show | jobs
by monkeybutton 1695 days ago
Google also runs their own public DNS servers which afaik Chrome defaults to. They can just sit server side waiting for DNS lookups of domains they've never seen before and queue them up for the Google bot. No browser telemetry needed.
2 comments
aix1 1695 days ago
> Google also runs their own public DNS servers which afaik Chrome defaults to.

The statement that Chrome does not honour the networking stack's DNS settings does not agree with my observational data. I run pi-hole DNS and Chrome absolutely fails to load domains blacklisted there.

link
ev1 1695 days ago
This is configurable, the default is to use the default network stack.

Settings > search for Use secure DNS for DNS-over-TLS.

link
mysterydip 1695 days ago
Why does chrome need to use DNS other than what I have set up through my IP stack? How does that work for inranet sites?
link
monkeybutton 1695 days ago
Because they see their solution as more secure. Intranet sites still work because Chrome only prefers their DNS first, it will still use your system settings if it doesn't work.
link