On Thu 30 Sep 2021 at 07:21:04 (-0400), Greg Wooledge wrote: > On Thu, Sep 30, 2021 at 12:38:29AM -0500, David Wright wrote: > > My usual strategy is to let the Debian installer set the dns server to > > IP address of the router, and configure the router to query 8.8.8.8/1.1.1.1. > > It's not ideal if you have a router that doesn't "belong" to you, > > ie that you can't configure yourself. > > > > Resolvconf squirrels that original address away in > > /etc/resolvconf/resolv.conf.d/original so that it can revert to it > > after you have left other networks/VPNs etc. So I guess that, at > > worst, you can just write in whatever you want into that file. > > Check it is still there after the next boot, and also check > > /etc/resolv.conf (which is a symlink) to make sure that it used it ok. > > /etc/resolv.conf *can* be a symlink, or not. Depends on what you've > installed. > > https://wiki.debian.org/resolv.conf
You snipped the last line that I quoted, which said "I also installed the package resolvconf because I need to use it with openvpn." Resolvconf is the subject of my paragraph. > This page doesn't talk about iwd... partly because I'd never heard of it > at the time I wrote most of the content on that page. I've certainly > never used it, and I don't know how it works, how resolvconf interacts > with it, etc. Nor I, but I certainly intend to try it out, and have read through that Arch wiki page. It (iwd) is in buster, but then, so is wicd, and I've been using wicd/wpa_supplicant for some years with no need to change. I'm somewhat surprised that there's been no reply from an iwd user. > It [wiki resolv.conf] also doesn't talk about systemd-networkd, or > network-manager. If > some people out there know how those things work (in *detail*) and > are able to contribute to the wiki page, that would be great. I haven't used either of those, nor ConnMan, but at the moment, I was treating resolvconf as a side dish, the main course being to get to ping something using iwd. Cheers, David.
