[08:59] <tuxick> is resolvconf really 'the' way to prevent system from overwriting resolv.conf?
[08:59] <tuxick> there's an awful lot of guesswork out there
[09:13] <mgedmin> no?  if /etc/resolv.conf is a regular file, nothing is supposed to overwrite it
[09:13] <mgedmin> by default /etc/resolv.conf is a symlink to /run/..., and the file in /run/ is the one being generated dynamically
[09:13] <tuxick> no it's not a file but a symlink
[09:13] <tuxick> ooh sorry
[09:14] <tuxick> hold on, is it that simple?
[09:15] <mgedmin> this was documented somewhere, but I'm skimming various README.Debian files trying to find an authoritative reference and failing
[09:15] <mgedmin> maybe it was mentioned in release notes for the ubuntu version that introduced systemd-resolved?
[09:16] <tuxick> good old days where you just configured resolv.conf :)
[09:19] <tuxick> dealing with a system i a network with AD on .local
[09:19] <tuxick> looks like systemd-resolved doesn't like that
[09:22] <tuxick> ok, verified on a test vm
[09:25] <tuxick> looks like systemd-resolved doesn't really like working with AD with a .local domain :)
[09:52] <mgedmin> oh, .local is used for mDNS
[09:52] <mgedmin> you may also need to check /etc/nsswitch.conf, it's possible that .local lookups get handled by the mdns resolver and never do dns queries
[09:53] <mgedmin> my nsswitch.conf has 'hosts: files mdns4_minimal [NOTFOUND=return] dns mymachines', and I never tweaked it myself, so it must be the default for ubuntu
[09:53] <mgedmin> to avoid headaches I would recommend not using .local as a LAN domain
[09:54] <tuxick> i laughed when i saw what they did
[09:55] <tuxick> worse: this is AD on network of a hospital
[09:56] <tuxick> anyway, replacing symlink with file does the trick
[09:56] <tuxick> so not going to bother with their mess
=== JanC is now known as Guest723
=== JanC is now known as Guest7379
=== JanC is now known as Guest3827