At Fri, 24 May 2024 11:59:23 -0700 CentOS mailing list <discuss@xxxxxxxxxxxxxxxx> wrote:
>
> Robert Heller wrote:
>
> > Normally, with systemd-resolved running /etc/resolv.conf is NOT an editable
> > file, but a symlink to a file under systemd-resolved control, and usually
> > systemd-resolved is running its own caching only name server (dmasq?) ...
>
> Kenneth Porter wrote:
>
> >Whether it's managed or not, CUPS is going to consult it when it uses
> >the resolver APIs in glibc. So you should be able to cat it to see what
> >the resolver APIs will use.
>
> Running "systemctl stop systemd-resolved" did not change the problem.
> On this system, /etc/resolv.conf is NOT a symlink. It contains only a
> single reference to the local BIND9 and a search statement with one
> argument.
Question: is dmasq running somewhere? Maybe "orphaned"?
--
Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364
Deepwoods Software -- Custom Software Services
http://www.deepsoft.com/ -- Linux Administration Services
heller@xxxxxxxxxxxx -- Webhosting Services
_______________________________________________
Discuss mailing list -- discuss@xxxxxxxxxxxxxxxx
To unsubscribe send an email to discuss-leave@xxxxxxxxxxxxxxxx
