James H. Markowitz
2022-10-31 15:48:10 UTC
I run my own DNS caching server, with a series of rules that
return the 127.0.0.1 IPv4 address (and ::1 IPv6) for a number of hosts
that I don't care about. Thus, when I try to connect to any facebook.com
site I just get redirected to 127.0.0.1 - where there is nothing running.
This worked as expected until recent versions of Chromium, where
it does not any more - such certainly is the case in the latest 107
version, but it may have been present already in 106. The thing is, it
seems to happen under Chromium and other browsers derived from the same
code alone - I tried under Opera and Firefox (where I made sure that DoH
is not enabled) and I get the behavior that I want: facebook.com is not
reachable. However, under Vivaldi and Chromium it is.
Is Chromium pulling a fast one on me? Anybody know how one can
make sure that Chromium is using my system-wide default DNS server,
rather than one of its choice under the wraps?
return the 127.0.0.1 IPv4 address (and ::1 IPv6) for a number of hosts
that I don't care about. Thus, when I try to connect to any facebook.com
site I just get redirected to 127.0.0.1 - where there is nothing running.
This worked as expected until recent versions of Chromium, where
it does not any more - such certainly is the case in the latest 107
version, but it may have been present already in 106. The thing is, it
seems to happen under Chromium and other browsers derived from the same
code alone - I tried under Opera and Firefox (where I made sure that DoH
is not enabled) and I get the behavior that I want: facebook.com is not
reachable. However, under Vivaldi and Chromium it is.
Is Chromium pulling a fast one on me? Anybody know how one can
make sure that Chromium is using my system-wide default DNS server,
rather than one of its choice under the wraps?