Google has a secret deal with FB called “Jedi Blue” that they knew was illegal

Re:Google has a secret deal with FB called “Jedi Blue” that ... by monkeybutton on Sunday October 24, 2021 @12:13PM (#28979258)

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.

[ Parent | on HN ]

Re:Google has a secret deal with FB called “Jedi Blue” that ... by aix1 on Sunday October 24, 2021 @02:14PM (#28980493)

> 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.

[ Parent | on HN ]

Re:Google has a secret deal with FB called “Jedi Blue” that ... by ev1 on Sunday October 24, 2021 @02:18PM (#28980541)

This is configurable, the default is to use the default network stack.

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

[ Parent | on HN ]

Re:Google has a secret deal with FB called “Jedi Blue” that ... by mysterydip on Sunday October 24, 2021 @12:38PM (#28979514)

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?

[ Parent | on HN ]

Re:Google has a secret deal with FB called “Jedi Blue” that ... by monkeybutton on Sunday October 24, 2021 @01:08PM (#28979832)

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.

[ Parent | on HN ]