On 1/22/2018 9:34 PM, James Knott wrote:
On 01/22/2018 05:42 PM, David C. Rankin wrote:
I have a strong suspicion... systemd and many of the newer network managers take control of resolv.conf (some do away with it completely and use a similarly named file). This has been a source of frustration. Worth a trip to: As I mentioned earlier, this computer has a static config for IPv4. Also, the domain name is provided by the IPv6 router advertisement.
Sorry James, I understood that. I wasn't clear. When you set a fixed/static network configuration, you would normally expect that to mean: "systemd or you network managers -- keep your bloody mitts off my resolv.conf" (and other config files), but there is no guarantee of that. I don't know off the top of my head where you tell systemd (or the other network managers) to not touch your setup, but there is a way to do it. When I stumbled through the first few configs with systemd, I recall wondering how Yast would deal with this stuff, but I haven't had openSuSE on a box with a fixed IP since the switch to systemd. On Arch, for a fixed IP, (I'm still using IPv4), I just use a minimal netctl service file and put a soft-link in /use/systemd/system/multi-user.target.wants/. Thankfully, netctl is one of the few systemd networks management schemes that continues with a traditional resolv.conf and has been problem free for my basic setup. All I care that resolve.conf does is resolve DNS searches for my domain (which it does not lose) on localhost and then Bind9/named.conf specifies the forwarders I want to use. That setup continues to work as it has since the beginning of time (well at least the last 17 years) I don't see why you can't do an IPv6 setup the same way. Make sure your host and domain name resolutions are working as expected (e.g. $ hostname and $hostname -f) as there have been some changes in gethostbyname and getdomainname a couple of years ago that did make subtle changes to what entries get drawn from where (the specifics escape me now). But if your host/domain name setup survives boot, there is no reason a simple static setup should have problems finding them. What Yast is doing behind the scenes -- I'm sorry I can't help there... -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org