On 23/2/23 18:23, daven...@tuxfamily.org wrote:
Hello,
On 2023-02-23 02:59, cono...@panix.com wrote:
On 2/22/23, daven...@tuxfamily.org <daven...@tuxfamily.org> wrote:
There is an unidentified process that decides it's ok to delete and
recreate /etc/resolv.conf without asking user/admin,
The problem is, the problematic process is not work's VPN related and
creates the file with wrong resolver's IP. The IP corresponds to my
home
router IP, which does has a DNS resolver and it works as it should. BUT
my home's router DNS obviously don't know jack about work internal
servers, on which I work… and work's proxy as well, which when it
cannot
be resolved… breaks everything using HTTP.
Might look at:
/etc/network/interfaces.d/setup
as explained in "man interfaces". (That file can/might be changed via
the network symbol in the window manager's configuration bar/menu
system, usually required with root/sudo privileges.)
John
There's nothing relevant to change in that file. I don't want to have
static IP. And the right interface name is not in it.
I'm not sure whether that file became totally obsoleled, or if it's
not normal that it doesn't contain the expected interface name? has it
been deprecated since debian switched to systemd so-called
"predictable" iface names?
For some reasons, since debian 9 or 10 (id nor 8?), including debian
11 new installs (work laptop has been install slightly more than a
year ago),
that files only contains the eth0 and local interfaces name, while
debian switched to systemd style interfaces names.
I remembrer having slowed down boots because of the that, on my
personal laptop, when debian switched to systemd style names and that
file still referred to eth0 which doesn't exist
So boot process was waiting for eth0 interface until I commented out
that part (eth0 block) of interfaces files.
On the newer work laptop on the other hand, there is that eth0 block,
there's is no eth0 interface on my system (there's enp.* and enx.*
systemd names, instead)
BUT I never had the slow/timeout-waiting boot process unlike the
personal was reinstall from zero instead of upgraded years ago only to
change HDD to SSD, and to change partitioning to encrypted LVM.
So my guess is /etc/network/interface.* has been replaced with
something also. Since it refers to non-exitent interfaces names
without breaking the network or slowing down the boot process.
Also, the switching to systemd styles interfaces names has been
following by a weird behaviour on my personal computer. It has a
"failed" error message at startup, for the network (or is networking?
it never remember the correct name) service, without breaking the
network… it weirdly just works. I never figured out what replaces that
service. If anyone has any idea?
As a general comment on resolving name service problems you need to
become acquainted with nsswitch
I have only recently become aware of it. It's central in determining
just how your system looks up lots of things including DNS names.
Some research and reading is required (for me and perhaps most?)
--
Jeremy
(Lists)
