[opensuse] Domain name doesn't stick
I'm running 42.3. One thing I've noticed is that the domain name, as entered in the Domain Name box, in Yast Network Settings, doesn't last through a reboot. It also gets removed from /etc/resolv.conf. Any idea why this happens? How to fix it? tnx jk -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
17.01.2018 20:06, James Knott пишет:
I'm running 42.3. One thing I've noticed is that the domain name, as entered in the Domain Name box, in Yast Network Settings,
Do you mean Hostname/DNS tab?
doesn't last through a reboot.
What exactly does it mean? Where you expect it, what files you check, what commands you use?
It also gets removed from /etc/resolv.conf.
When it appears in resolv.conf before it gets removed?
Any idea why this happens? How to fix it?
tnx jk
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/17/2018 12:16 PM, Andrei Borzenkov wrote:
17.01.2018 20:06, James Knott пишет:
I'm running 42.3. One thing I've noticed is that the domain name, as entered in the Domain Name box, in Yast Network Settings, Do you mean Hostname/DNS tab?
Yes.
doesn't last through a reboot.
What exactly does it mean? Where you expect it, what files you check, what commands you use?
It means that after a reboot, it's no longer in resolv.conf nor in Network Settings on the Hostname/DNS tab.
It also gets removed from /etc/resolv.conf.
When it appears in resolv.conf before it gets removed?
Yes. Of course it's in resolv.conf. It's saved there when saved in Yast and disappears from both on reboot. The resolv.conf file shows a write date & time corresponding to the reboot. So, something is writing to resolv.conf, without the domain name.
Any idea why this happens? How to fix it?
tnx jk
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-01-17 18:36, James Knott wrote:
On 01/17/2018 12:16 PM, Andrei Borzenkov wrote:
17.01.2018 20:06, James Knott пишет:
I'm running 42.3. One thing I've noticed is that the domain name, as entered in the Domain Name box, in Yast Network Settings, Do you mean Hostname/DNS tab?
Yes.
doesn't last through a reboot.
What exactly does it mean? Where you expect it, what files you check, what commands you use?
It means that after a reboot, it's no longer in resolv.conf nor in Network Settings on the Hostname/DNS tab.
It also gets removed from /etc/resolv.conf.
When it appears in resolv.conf before it gets removed?
Yes. Of course it's in resolv.conf. It's saved there when saved in Yast and disappears from both on reboot. The resolv.conf file shows a write date & time corresponding to the reboot. So, something is writing to resolv.conf, without the domain name.
Change hostname from dhcp server is active in YaST network settings, perhaps? -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 01/17/2018 12:47 PM, Carlos E. R. wrote:
Yast and disappears from both on reboot. The resolv.conf file shows a write date & time corresponding to the reboot. So, something is writing to resolv.conf, without the domain name. Change hostname from dhcp server is active in YaST network settings,
Yes. Of course it's in resolv.conf. It's saved there when saved in perhaps?
I don't use DHCP on that computer. Static config only. Also, the IPv6 router advertisements are providing the domain name, but I can't resolve local hosts, unless I include the domain name. Manually adding it to Hostname/DNS makes that work again. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-01-17 18:52, James Knott wrote:
On 01/17/2018 12:47 PM, Carlos E. R. wrote:
Yast and disappears from both on reboot. The resolv.conf file shows a write date & time corresponding to the reboot. So, something is writing to resolv.conf, without the domain name. Change hostname from dhcp server is active in YaST network settings,
Yes. Of course it's in resolv.conf. It's saved there when saved in perhaps?
I don't use DHCP on that computer. Static config only. Also, the IPv6 router advertisements are providing the domain name, but I can't resolve local hosts, unless I include the domain name. Manually adding it to Hostname/DNS makes that work again.
I know, it doesn't matter. It is a different tick box in YaST. Please humour me and check it up :-) -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 01/17/2018 01:24 PM, Carlos E. R. wrote:
Change hostname from dhcp server is active in YaST network settings,
perhaps?
I don't use DHCP on that computer. Static config only. Also, the IPv6 router advertisements are providing the domain name, but I can't resolve local hosts, unless I include the domain name. Manually adding it to Hostname/DNS makes that work again. I know, it doesn't matter. It is a different tick box in YaST. Please humour me and check it up :-)
I assume you mean Set Hostname via DHCP. It's set to no. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-01-17 20:31, James Knott wrote:
On 01/17/2018 01:24 PM, Carlos E. R. wrote:
Change hostname from dhcp server is active in YaST network settings,
perhaps?
I don't use DHCP on that computer. Static config only. Also, the IPv6 router advertisements are providing the domain name, but I can't resolve local hosts, unless I include the domain name. Manually adding it to Hostname/DNS makes that work again. I know, it doesn't matter. It is a different tick box in YaST. Please humour me and check it up :-)
I assume you mean Set Hostname via DHCP. It's set to no.
Yes, that's what I meant. Well, the cases I have seen it was that. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
17.01.2018 20:36, James Knott пишет:
On 01/17/2018 12:16 PM, Andrei Borzenkov wrote:
17.01.2018 20:06, James Knott пишет:
I'm running 42.3. One thing I've noticed is that the domain name, as entered in the Domain Name box, in Yast Network Settings, Do you mean Hostname/DNS tab?
Yes.
What are other settings (nameservers, DNS policy)?
doesn't last through a reboot.
What exactly does it mean? Where you expect it, what files you check, what commands you use?
It means that after a reboot, it's no longer in resolv.conf nor in Network Settings on the Hostname/DNS tab.
What "hostname" and "hostname -d" say? What /etc/hostname contains before and after reboot?
It also gets removed from /etc/resolv.conf.
That's likely side effect of something else, file is rebuilt every time network configuration changes. Most likely your hostname changes.
When it appears in resolv.conf before it gets removed?
Yes. Of course it's in resolv.conf. It's saved there when saved in Yast and disappears from both on reboot. The resolv.conf file shows a write date & time corresponding to the reboot. So, something is writing to resolv.conf, without the domain name.
Any idea why this happens? How to fix it?
tnx jk
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
17.01.2018 21:04, Andrei Borzenkov пишет:
17.01.2018 20:36, James Knott пишет:
On 01/17/2018 12:16 PM, Andrei Borzenkov wrote:
17.01.2018 20:06, James Knott пишет:
I'm running 42.3. One thing I've noticed is that the domain name, as entered in the Domain Name box, in Yast Network Settings, Do you mean Hostname/DNS tab?
Yes.
What are other settings (nameservers, DNS policy)?
doesn't last through a reboot.
What exactly does it mean? Where you expect it, what files you check, what commands you use?
It means that after a reboot, it's no longer in resolv.conf nor in Network Settings on the Hostname/DNS tab.
What "hostname" and "hostname -d" say? What /etc/hostname contains before and after reboot?
It also gets removed from /etc/resolv.conf.
That's likely side effect of something else, file is rebuilt every time network configuration changes. Most likely your hostname changes.
Also any difference in "grep NETCONFIG_ /etc/sysconfig/network/config" before and after reboot? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/17/2018 02:37 PM, Michael Hamilton wrote:
On Thu, 18 Jan 2018, Andrei Borzenkov wrote:
What /etc/hostname contains before and after reboot? It would be interesting/revealing to see the answer to the above.
It currently shows the host name and I'll check again when I reboot. However, the problem is not about the host name. It's about the domain name disappearing. As I mentioned in another note, I use pfSense for my local DNS. It has the host name and domain name included for each entry. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-01-17 20:47, James Knott wrote:
On 01/17/2018 02:37 PM, Michael Hamilton wrote:
On Thu, 18 Jan 2018, Andrei Borzenkov wrote:
What /etc/hostname contains before and after reboot? It would be interesting/revealing to see the answer to the above.
It currently shows the host name and I'll check again when I reboot. However, the problem is not about the host name. It's about the domain name disappearing.
Ah, sorry, I didn't catch that detail. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On Thu, 18 Jan 2018, James Knott wrote:
On 01/17/2018 02:37 PM, Michael Hamilton wrote:
On Thu, 18 Jan 2018, Andrei Borzenkov wrote:
What /etc/hostname contains before and after reboot? It would be interesting/revealing to see the answer to the above.
It currently shows the host name and I'll check again when I reboot. However, the problem is not about the host name. It's about the domain name disappearing.
As I mentioned in another note, I use pfSense for my local DNS. It has the host name and domain name included for each entry.
It's been a while, and things have changed, but in the past, the fully qualified hostname should be the first entry for the static address in the hosts file, for example: 10.0.0.20 kosmos1.gentoo.co.nz kosmos1 So I wondered if this was the case here. If it isn't you might try manually setting it that way. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/17/2018 04:52 PM, Michael Hamilton wrote:
As I mentioned in another note, I use pfSense for my local DNS. It has
the host name and domain name included for each entry.
It's been a while, and things have changed, but in the past, the fully qualified hostname should be the first entry for the static address in the hosts file, for example:
10.0.0.20 kosmos1.gentoo.co.nz kosmos1
So I wondered if this was the case here. If it isn't you might try manually setting it that way.
As I mentioned, the problem is the domain name disappearing from /etc/resolv.conf. Resolv.conf normally contains a search line, that contains the domain name. That line is there after I save it, but is gone after reboot. Something is causing that file to be written without that search line. When that line is there, I can do a host lookup using only the host name. When it's not, I can't. This has nothing to do with /etc/hosts, as I am not using that file on this computer for name resolution. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op woensdag 17 januari 2018 23:10:26 CET schreef James Knott:
On 01/17/2018 04:52 PM, Michael Hamilton wrote:
As I mentioned in another note, I use pfSense for my local DNS. It has
the host name and domain name included for each entry.
It's been a while, and things have changed, but in the past, the fully qualified hostname should be the first entry for the static address in the hosts file, for example:
10.0.0.20 kosmos1.gentoo.co.nz kosmos1
So I wondered if this was the case here. If it isn't you might try manually setting it that way.
As I mentioned, the problem is the domain name disappearing from /etc/resolv.conf. Resolv.conf normally contains a search line, that contains the domain name. That line is there after I save it, but is gone after reboot. Something is causing that file to be written without that search line. When that line is there, I can do a host lookup using only the host name. When it's not, I can't. This has nothing to do with /etc/hosts, as I am not using that file on this computer for name resolution.
Look for NETCONFIG_DNS_STATIC_SEARCHLIST= in /etc/sysconfig/network/config The values of this parameter will be put in /etc/resolv.conf in the searchlist with domain name(s) each time the network is started. It is there for static network configurations. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/18/2018 04:50 AM, Freek de Kruijf wrote:
Look for NETCONFIG_DNS_STATIC_SEARCHLIST= in /etc/sysconfig/network/config The values of this parameter will be put in /etc/resolv.conf in the searchlist with domain name(s) each time the network is started. It is there for static network configurations.
At the moment, it shows my domain name. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/17/2018 01:04 PM, Andrei Borzenkov wrote:
What are other settings (nameservers, DNS policy)?
> doesn't last > through a reboot.
What exactly does it mean? Where you expect it, what files you check, what commands you use?
It means that after a reboot, it's no longer in resolv.conf nor in Network Settings on the Hostname/DNS tab. What "hostname" and "hostname -d" say? What /etc/hostname contains before and after reboot?
Hostname shows the hostname & hostname -d doesn't show anything. Host shows the full host name and domain, along with the IPv4 and IPv6 addresses, before reboot, but can't find the host after, unless I add the domain. I'm running pfSense as my firewall router, which included DNS resolver.
> It also gets removed from /etc/resolv.conf. >
That's likely side effect of something else, file is rebuilt every time network configuration changes. Most likely your hostname changes.
I am not changing anything. I have a static configuration on this computer. The only thing that happens automatically is IPv6 SLAAC address and the router advertisement, which contain the correct domain name. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op woensdag 17 januari 2018 18:06:23 CET schreef James Knott:
I'm running 42.3. One thing I've noticed is that the domain name, as entered in the Domain Name box, in Yast Network Settings, doesn't last through a reboot. It also gets removed from /etc/resolv.conf.
Any idea why this happens? How to fix it?
tnx jk
I filed a bug report about this on 2015-07-16. https://bugzilla.opensuse.org/show_bug.cgi?id=938402 -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/17/2018 12:06 PM, James Knott wrote:
I'm running 42.3. One thing I've noticed is that the domain name, as entered in the Domain Name box, in Yast Network Settings, doesn't last through a reboot. It also gets removed from /etc/resolv.conf.
Any idea why this happens? How to fix it?
tnx jk
I have found a work around, put the domain name in the Domain Search box, rather than Domain Name. It stays there and in resolv.conf. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/17/2018 11:06 AM, James Knott wrote:
I'm running 42.3. One thing I've noticed is that the domain name, as entered in the Domain Name box, in Yast Network Settings, doesn't last through a reboot. It also gets removed from /etc/resolv.conf.
Any idea why this happens? How to fix it?
tnx jk
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: https://wiki.archlinux.org/index.php/Network_configuration and https://wiki.archlinux.org/index.php/Wicd -- 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
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. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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
James Knott wrote:
I'm running 42.3. One thing I've noticed is that the domain name, as entered in the Domain Name box, in Yast Network Settings, doesn't last through a reboot. It also gets removed from /etc/resolv.conf.
Any idea why this happens? How to fix it?
My first thought was it might be something sysd is doing -- but call that an *unsubstantiated* feeling. Then I thought about how to figure it out... You say /etc/defaultdomain's contents are changed. Try, as root, setting the immutable bit on the file: sudo chattr +i /etc/defaultdomain. Now when you reboot, **hopefully**, you will see an error message about how the file can't be written to (unless someone also toggles the immutable bit to write to it (which would be rather evil)). Just a guess...sorry didn't answer sooner...lack of enthusiasm on my part... :-/ -l -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/24/2018 04:28 PM, L A Walsh wrote:
James Knott wrote:
I'm running 42.3. One thing I've noticed is that the domain name, as entered in the Domain Name box, in Yast Network Settings, doesn't last through a reboot. It also gets removed from /etc/resolv.conf.
Any idea why this happens? How to fix it?
My first thought was it might be something sysd is doing -- but call that an *unsubstantiated* feeling.
Then I thought about how to figure it out...
You say /etc/defaultdomain's contents are changed.
Try, as root, setting the immutable bit on the file:
sudo chattr +i /etc/defaultdomain.
Now when you reboot, **hopefully**, you will see an error message about how the file can't be written to (unless someone also toggles the immutable bit to write to it (which would be rather evil)).
Just a guess...sorry didn't answer sooner...lack of enthusiasm on my part... :-/
-l
That file is empty and shows a write date of May 17, so I don't think that's the problem. As I mentioned earlier, /etc/resolv.conf was changed to remove the search domain. However, I have found a work around. I found that if I put the domain name in the search domain box, rather than domain name, the search domain stays in resolv.conf and works as expected. There is clearly a bug here, but someone else reported it earlier.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
You say /etc/defaultdomain's contents are changed.
--- If above is false, then apply the debugging measures to the one that *IS* changing. Whichever. I.e. if its another file, then make that one immutable so if anyone tries to write to it you can catch it.
As I mentioned earlier, /etc/resolv.conf was changed to remove the search domain.
Ahh, too many responses -- couldn't see where you mentioned what file changed. I'm sure you mentioned it, but started to be too many responses to go through again.
However, I have found a work around. I found that if I put the domain name in the search domain box,...
if the workaround works for you, *great*. I just "overfocused" on this:
Any idea why this happens? How to fix it?
I just figured tossing out an error when someone tried to change it might help track it down. :-) -l -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-ID: <alpine.LSU.2.21.1801242341330.28710@Telcontar.valinor> On Wednesday, 2018-01-24 at 13:28 -0800, L A Walsh wrote:
James Knott wrote:
I'm running 42.3. One thing I've noticed is that the domain name, as entered in the Domain Name box, in Yast Network Settings, doesn't last through a reboot. It also gets removed from /etc/resolv.conf.
Any idea why this happens? How to fix it?
My first thought was it might be something sysd is doing -- but call that an *unsubstantiated* feeling.
Then I thought about how to figure it out...
You say /etc/defaultdomain's contents are changed.
Try, as root, setting the immutable bit on the file:
sudo chattr +i /etc/defaultdomain.
Now when you reboot, **hopefully**, you will see an error message about how the file can't be written to (unless someone also toggles the immutable bit to write to it (which would be rather evil)).
That trick can fail some times :-P There is another one with AppArmour. From: Cristian Rodríguez <> Date: Fri, 06 Mar 2009 12:04:21 -0300 +++-------------------------- try this: # auditctl -w /dev/null -p a # auditctl -e 1 and then watch the logs... if auditctl is not found, when you execute it as root, install package "audit" - --------------------------++- - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlppDEAACgkQtTMYHG2NR9UD1ACfRhKwT4YA90owrPBPgdZ6jQQl DXMAnRR0UqrbWKJxxTBA4r52eGc7fr9n =zwbk -----END PGP SIGNATURE-----
participants (7)
-
Andrei Borzenkov -
Carlos E. R. -
David C. Rankin -
Freek de Kruijf -
James Knott -
L A Walsh -
Michael Hamilton