to...@tuxteam.de wrote: > [-- text/plain, encoding quoted-printable, charset: utf-8, 29 lines --] > > On Wed, Jan 22, 2025 at 09:48:30AM +0700, Max Nikulin wrote: > > On 21/01/2025 23:31, to...@tuxteam.de wrote: > > > On Tue, Jan 21, 2025 at 10:38:51PM +0700, Max Nikulin wrote: > > > > On 19/01/2025 17:21, mick.crane wrote: > > > > > The other day changed the ISP's (Sky) router to have fibre connection. > > > > Maybe the previous router was configured to serve .home DNS zone. > > > Judging by the other symptoms (ping working, browser not) the resolver > > > in the box is OK (the .home names are resolved in /etc/hosts). > > > > I have read somewhere that chromium may read /etc/resolv.conf and send > > requests to the specified servers directly bypassing /etc/nsswitch.conf. > > (The statement needs verification.) > > Oh, goody. > > [interesting stuff snipped] > > > > At least cloudflare and google do not resolve the host name (other DoH > > provider may behave in a different way) > > But most probably not in the way the OP expects, since they can't read > (?) their local /etc/hosts... > Surely in many cases DNS gets farmed out to a router to which the web browser (whether Chromium based or not) doesn't have any sort of direct access so it can't really dig around in the configuration.
I have removed nearly all the 'extra' DNS configuration (i.e. anything like systemd's resolver and local DNS caching) in my main Linux systems. I run dnsmasq on my router with a blacklist configuration so ad-blocking works for every system on the LAN (it confuses visitors sometimes when they don't see the usual adverts on their 'phones). I run Vivaldi and it seems to behave fairly as one would expect in this environment. -- Chris Green ยท
